| 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: <20130313160623.52ec76cd5239c791b59828b8@linux-foundation.org> Date: Wed, 13 Mar 2013 16:06:23 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Miklos Szeredi <miklos@...redi.hu> Cc: viro@...IV.linux.org.uk, torvalds@...ux-foundation.org, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, hch@...radead.org, apw@...onical.com, nbd@...nwrt.org, neilb@...e.de, jordipujolp@...il.com, ezk@....cs.sunysb.edu, dhowells@...hat.com, sedat.dilek@...glemail.com, hooanon05@...oo.co.jp, mszeredi@...e.cz Subject: Re: [PATCH 8/9] overlay: overlay filesystem documentation On Wed, 13 Mar 2013 15:16:32 +0100 Miklos Szeredi <miklos@...redi.hu> wrote: > From: Neil Brown <neilb@...e.de> > > Document the overlay filesystem. > Damn, I did it again. This is good, thanks. > +Changes to the underlying filesystems while part of a mounted overlay > +filesystem are not allowed. If the underlying filesystem is changed, > +the behavior of the overlay is undefined, though it will not result in > +a crash or deadlock. ah-hah, there it is. I was wondering how this can-o-worms would be handled ;) Is there anything in place to enforce this at runtime? Checks for read-onlyness, code to prevent rw remounts, etc? -- 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