linux-kernel - Re: [BUG] remount ro on loopback mount leaves unmountable filesystem behind

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080513124203.GA4806@infradead.org>
Date:	Tue, 13 May 2008 08:42:03 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	David Chinner <dgc@....com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	util-linux-ng@...r.kernel.org
Subject: Re: [BUG] remount ro on loopback mount leaves unmountable
	filesystem behind

On Tue, May 13, 2008 at 10:07:10PM +1000, David Chinner wrote:
> Anyway, I'll hard code loop device numbers into the script so
> I can just forget about this problem. Thanks, Christoph.

hardcoding them is a little dangerous because a system might aswell
have them in use already, e.g. for CD images.  Just use losetup -f to
find the first free one and keep it in a shell variable.
--
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/