linux-kernel - Re: [PATCH 2/2] block: clear ro on fd detach fd is bound

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 for Android: free password hash cracker in your pocket

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

Message-ID: <7965.1295832488@jrobl>
Date:	Mon, 24 Jan 2011 10:28:08 +0900
From:	"J. R. Okajima" <hooanon05@...oo.co.jp>
To:	Tejun Heo <tj@...nel.org>
Cc:	Jens Axboe <axboe@...nel.dk>,
	David Brownell <dbrownell@...rs.sourceforge.net>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	Al Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH 2/2] block: clear ro on fd detach fd is bound


Tejun Heo:
> Commit 75f1dc0d (block: check bdev_read_only() from blkdev_get())
> enforced bdev_read_only() check during blkdev_get().  This had an
> unfortunate side effect on loop because loop didn't clear ro flag on
> fd detach, so once a loop device was used ro, it can't be used for rw
> at all.
>
> Fix it by clearing ro flag on fd detach.

Tested and succeeded, thanx.


J. R. Okajima
--
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/