The patch titled
drivers/block/loop.c: emit uevent on auto release
has been added to the -mm tree. Its filename is
drivers-block-loopc-emit-uevent-on-auto-release.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: drivers/block/loop.c: emit uevent on auto release
From: Phillip Susi <psusi@xxxxxxxxxx>
Fix the loopback device to emit a uevent on auto release. The loopback
driver failed to emit the change uevent when auto releasing the device.
Fix lo_release() to pass the bdev to loop_clr_fd() so it can emit the
event.
Cc: Jens Axboe <axboe@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/block/loop.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/block/loop.c~drivers-block-loopc-emit-uevent-on-auto-release drivers/block/loop.c
--- a/drivers/block/loop.c~drivers-block-loopc-emit-uevent-on-auto-release
+++ a/drivers/block/loop.c
@@ -1509,7 +1509,7 @@ static int lo_release(struct gendisk *di
* In autoclear mode, stop the loop thread
* and remove configuration after last close.
*/
- err = loop_clr_fd(lo, NULL);
+ err = loop_clr_fd(lo, lo->lo_device);
if (!err)
goto out_unlocked;
} else {
_
Patches currently in -mm which might be from psusi@xxxxxxxxxx are
drivers-block-loopc-emit-uevent-on-auto-release.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
