linux-kernel - [PATCH 1/2] Fixed loopback device to emit uevent on auto release

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4e667c8b.kbjARDpYtcTuZVKx%ayan.george@canonical.com>
Date:	Tue, 06 Sep 2011 20:03:23 +0000
From:	Ayan George <ayan@...n.net>
To:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	psusi@....rr.com
Subject: [PATCH 1/2] Fixed loopback device to emit uevent on auto release

At Andrew Norton's request, I've split up my API cleanup patches into two.
Below is Phillip Susi's uevent notification fix and the second part of the
patch is the API cleanup.

>From e0a49665093b7e8289e3c733f4aa0e17e11c0c10 Mon Sep 17 00:00:00 2001
From: Phillip Susi <psusi@....rr.com>
Date: Tue, 6 Sep 2011 15:07:30 -0400
Subject: [PATCH 1/2] Fixed loopback device to emit uevent on auto release

The loopback driver failed to emit the change uevent
when auto releasing the device.  Fixed lo_release()
to pass the bdev to loop_clr_fd() so it can emit
the event.

Signed-off-by: Phillip Susi <psusi@....rr.com>
---
 drivers/block/loop.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 4720c7a..6d0f28d 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -1513,7 +1513,7 @@ static int lo_release(struct gendisk *disk, fmode_t mode)
 		 * 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 {
-- 
1.7.4.1


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/