linux-kernel - Re: [PATCH] Allow auto-destruction of loop devices.

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

Date:	Tue, 30 Oct 2007 13:17:29 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	bernie@...ewiz.org
Subject: Re: [PATCH] Allow auto-destruction of loop devices.

On Tue, 30 Oct 2007 16:12:51 -0400
David Woodhouse <dwmw2@...radead.org> wrote:

> On Tue, 2007-10-30 at 13:01 -0700, Andrew Morton wrote:
> > Why do we want to do this?
> 
> In general, so that we can automatically allocate loop devices (as with
> losetup -f) and have them disappear when we're done with them.
> 
> In particular, right now, so that we can stop relying on the hackish
> special-case in umount(8) which kills off loop devices which were set up
> by 'mount -oloop'. That means we can stop putting crap in /etc/mtab
> which doesn't belong there, which means it can be a symlink
> to /proc/mounts, which means yet another writable file on the root
> filesystem is eliminated and the 'stateless' folks get happier... and
> OLPC trac #356 can be closed.
> 
> The mount(8) side of that is at
> http://marc.info/?l=util-linux-ng&m=119362955431694&w=2

ooh, I spy a changelog.  Thanks.
-
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/