summaryrefslogtreecommitdiffstats
path: root/rust/helpers/helpers.c
diff options
context:
space:
mode:
authorThomas Weißschuh <thomas.weissschuh@linutronix.de>2025-04-15 10:51:47 +0200
committerJens Axboe <axboe@kernel.dk>2025-04-15 08:58:42 -0600
commite7bc0010ceb403d025100698586c8e760921d471 (patch)
treee83542550ffbfa5aacac472a4b616da193f1b28e /rust/helpers/helpers.c
parent1fdb8188c3d505452b40cdb365b1bb32be533a8e (diff)
downloadlinux-e7bc0010ceb403d025100698586c8e760921d471.tar.gz
linux-e7bc0010ceb403d025100698586c8e760921d471.tar.bz2
linux-e7bc0010ceb403d025100698586c8e760921d471.zip
loop: properly send KOBJ_CHANGED uevent for disk device
The original commit message and the wording "uncork" in the code comment indicate that it is expected that the suppressed event instances are automatically sent after unsuppressing. This is not the case, instead they are discarded. In effect this means that no "changed" events are emitted on the device itself by default. While each discovered partition does trigger a changed event on the device, devices without partitions don't have any event emitted. This makes udev miss the device creation and prompted workarounds in userspace. See the linked util-linux/losetup bug. Explicitly emit the events and drop the confusingly worded comments. Link: https://github.com/util-linux/util-linux/issues/2434 Fixes: 498ef5c777d9 ("loop: suppress uevents while reconfiguring the device") Cc: stable@vger.kernel.org Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de> Link: https://lore.kernel.org/r/20250415-loop-uevent-changed-v2-1-0c4e6a923b2a@linutronix.de Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'rust/helpers/helpers.c')
0 files changed, 0 insertions, 0 deletions