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
| ||
|
Message-ID: <Pine.LNX.4.64.0710302104020.31325@fbirervta.pbzchgretzou.qr> Date: Tue, 30 Oct 2007 21:05:43 +0100 (CET) From: Jan Engelhardt <jengelh@...putergmbh.de> To: Andrew Morton <akpm@...ux-foundation.org> cc: David Woodhouse <dwmw2@...radead.org>, torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org, bernie@...ewiz.org Subject: Re: [PATCH] Allow auto-destruction of loop devices. On Oct 30 2007 13:01, Andrew Morton wrote: >On Sun, 28 Oct 2007 19:08:31 -0400 >David Woodhouse <dwmw2@...radead.org> wrote: > >> This allows a flag to be set on loop devices so that when they are >> closed for the last time, they'll self-destruct. >> > >Why do we want to do this? Off the top of my head, lazy unmounting comes to mind. Think of this: mount foobar /mnt -o loop; cd /mnt; umount /mnt; Currently, this leaves /dev/loop0 assigned, either chewing up loop places or needlessy exposing objects meant to be rather not accessible. (Think cryptoloop devices -- and pam_mount.) BTW, such a flag would also really be useful for dm(-crypt). - 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/
Powered by blists - more mailing lists