| 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: <20060904125744.GA1961@wohnheim.fh-wedel.de> Date: Mon, 4 Sep 2006 14:57:44 +0200 From: Jörn Engel <joern@...nheim.fh-wedel.de> To: Pavel Machek <pavel@...e.cz> Cc: Josef Sipek <jsipek@...sunysb.edu>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, hch@...radead.org, akpm@...l.org, viro@....linux.org.uk Subject: Re: [PATCH 00/22][RFC] Unionfs: Stackable Namespace Unification Filesystem On Sun, 3 September 2006 11:05:08 +0000, Pavel Machek wrote: > > > - Modifying a Unionfs branch directly, while the union is mounted, is > > currently unsupported. Any such change may cause Unionfs to oops and it > > can even result in data loss! > > I'm not sure if that is acceptable. Even root user should be unable to > oops the kernel using 'normal' actions. Direct modification of branches is similar to direct modification of block devices underneith a mounted filesystem. While I agree that such a thing _should_ not oops the kernel, I'd bet that you can easily run a stresstest on a filesystem while randomly flipping bits in the block device and get just that. There are bigger problems in unionfs to worry about. Jörn -- Simplicity is prerequisite for reliability. -- Edsger W. Dijkstra - 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