summaryrefslogtreecommitdiffstats
path: root/fs/sysfs/mount.c
diff options
context:
space:
mode:
authorDavid Zeuthen <davidz@redhat.com>2010-05-03 14:08:59 +0200
committerGreg Kroah-Hartman <gregkh@suse.de>2010-05-21 18:37:30 +0200
commitc3473c63542d53740f175f3a515257ae159e998b (patch)
tree20832b70ba6f89aacaa377d41b7427d74be647b1 /fs/sysfs/mount.c
parentDriver core: Protect device shutdown from hot unplug events. (diff)
downloadlinux-c3473c63542d53740f175f3a515257ae159e998b.tar.xz
linux-c3473c63542d53740f175f3a515257ae159e998b.zip
generate "change" uevent for loop device
Recent udev versions probe loop devices for filesystems meaning that the /dev/disk hierarchy may contain useful entries such as $ ls -l /dev/disk/by-label/Fedora-12-x86_64-Live lrwxrwxrwx 1 root root 11 Mar 11 13:41 /dev/disk/by-label/Fedora-12-x86_64-Live -> ../../loop0 Unfortunately, no "change" uevent is generated when the loop device is detached so the symlink persists. Additionally, no "change" uevent is guaranteed to be generated when attaching an fd or changing capacity. For example, user space could open the loop device O_RDONLY (in fact, recent util-linux-ng does this) so udev's OPTIONS+="watch" machinery may not trigger the "change" uevent. This patch ensures that the "change" uevent is generated in all of these cases. As a result, the /dev/disk hierarchy works as expected for loop devices. Signed-off-by: David Zeuthen <davidz@redhat.com> Acked-by: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'fs/sysfs/mount.c')
0 files changed, 0 insertions, 0 deletions