On Friday, 05/21/2021 at 12:44 GMT, Ingo Adlung <[email protected]> wrote: > I don't recall how an unsolicited DE is processed today, but I don't feel a > udev event would be the adequate action. Perhaps it could become an > informational log entry that could be filtered ...
There's already code in vmur to handle unsolicited DE (it explicitly ignores it). I'm not sure how add_uevent_var() works and how drivers can change the value of variable with kobject_uevent( KOBJ_CHANGE ), but maybe vmur could add "NEW_SPOOL_FILE" when it gets loaded, and change it's status when the unsolicited DE arrives. (Also triggered by CP READY 00C command._ Udev appears to be designed to handle device status changes, not just hotplug events. Alan Altmark Senior Managing z/VM and Linux Consultant IBM Systems Lab Services IBM Z Delivery Practice ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 [email protected] IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
