aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-strncpy-src.c
diff options
context:
space:
mode:
authorPeter Oberparleiter <[email protected]>2022-09-26 16:56:04 +0200
committerVasily Gorbik <[email protected]>2022-10-10 10:15:10 +0200
commitbf18140d30541c2c1e5c0f57879634f3d0d04912 (patch)
treee2262b24434363982790b447024478181207cf52 /lib/test_fortify/write_overflow-strncpy-src.c
parentf3e59ff348c077a6afd4edb23d7e69e9cba62fdc (diff)
s390/vmur: generate uevent on unsolicited device end
When a traditional channel-attached device transitions from not-ready to ready state, an unsolicited DEVICE END I/O interrupt is raised. This happens for example when a new file arrives in the z/VM virtual reader device. Change the Linux kernel to generate a change uevent when such an interrupt occurs for any online unit record devices supported by the vmur driver. This can be useful to automatically trigger processing of files as they arrive in the reader device. A sample udev rule for running a program when this event occurs looks as follows: ENV{DRIVER}=="vmur", ACTION=="change", ENV{EVENT}=="unsol_de", \ RUN{program}="/path/to/program" The rule can be tested using the following steps: 1. Set reader device online (assuming default reader device number 000c) $ chzdev -ea 0.0.000c 2. Force a ready-state transition using z/VM's READY CP command $ vmcp ready 000c Suggested-by: Alan Altmark <[email protected]> Reviewed-by: Heiko Carstens <[email protected]> Reviewed-by: Sven Schnelle <[email protected]> Signed-off-by: Peter Oberparleiter <[email protected]> Signed-off-by: Vasily Gorbik <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions