summaryrefslogtreecommitdiff
path: root/drivers/md/dm.c
diff options
context:
space:
mode:
authorHannes Reinecke <hare@suse.de>2006-10-03 08:15:35 (GMT)
committerLinus Torvalds <torvalds@g5.osdl.org>2006-10-03 15:04:15 (GMT)
commit8560ed6fa8d43537af558514fa48f670b3349f08 (patch)
treee5efdfbba841c3f4c4a485ba4e39a3117c75acdc /drivers/md/dm.c
parente69fae561f422f7f9dbda19f448633aa6564663e (diff)
downloadlinux-fsl-qoriq-8560ed6fa8d43537af558514fa48f670b3349f08.tar.xz
[PATCH] dm: add uevent change event on resume
Device-mapper devices are not accessible until a 'resume' ioctl has been issued. For userspace to find out when this happens we need to generate an uevent for udev to take appropriate action. As discussed at OLS we should send 'change' events for 'resume'. We can think of no useful purpose served by also having 'suspend' events. Signed-off-by: Hannes Reinecke <hare@suse.de> Signed-off-by: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by: Alasdair G Kergon <agk@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'drivers/md/dm.c')
-rw-r--r--drivers/md/dm.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/md/dm.c b/drivers/md/dm.c
index 81717e2..883860c 100644
--- a/drivers/md/dm.c
+++ b/drivers/md/dm.c
@@ -1378,6 +1378,8 @@ int dm_resume(struct mapped_device *md)
dm_table_unplug_all(map);
+ kobject_uevent(&md->disk->kobj, KOBJ_CHANGE);
+
r = 0;
out: