Changes between Initial Version and Version 1 of Ticket #4745, comment 9
- Timestamp:
- 12/02/2020 05:11:30 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4745, comment 9
initial v1 1 1 2 {{{ 2 3 3 CHANGES WITH 247: 4 4 5 *KERNEL API INCOMPATIBILITY: Linux 4.14 introduced two new uevents5 KERNEL API INCOMPATIBILITY: Linux 4.14 introduced two new uevents 6 6 "bind" and "unbind" to the Linux device model. When this kernel 7 7 change was made, systemd-udevd was only minimally updated to handle … … 50 50 handle the new events. Specifically: 51 51 52 •All rule files that currently use a header guard similar to52 - All rule files that currently use a header guard similar to 53 53 ACTION!="add|change",GOTO="xyz_end" should be updated to use 54 54 ACTION=="remove",GOTO="xyz_end" instead, so that the … … 60 60 future kernel uevent type additions). 61 61 62 •Similarly, all code monitoring devices that contains an 'if' branch62 - Similarly, all code monitoring devices that contains an 'if' branch 63 63 discerning the "add" + "change" uevent actions from all other 64 64 uevents actions (i.e. considering devices only relevant after "add" … … 73 73 accessing the device should then be handled gracefully. 74 74 75 •Any code that uses device tags for deciding whether a device is75 - Any code that uses device tags for deciding whether a device is 76 76 relevant or not most likely needs to be updated to use the new 77 77 udev_device_has_current_tag() API (or sd_device_has_current_tag() … … 687 687 688 688 – Warsaw, 2020-11-26 689 }}} 689