linux-kernel - Re: [PATCH 00/22][RFC] Unionfs: Stackable Namespace Unification Filesystem

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1157376506.4398.15.camel@localhost.localdomain>
Date:	Mon, 04 Sep 2006 09:28:26 -0400
From:	Shaya Potter <spotter@...columbia.edu>
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, 2006-09-03 at 11:05 +0000, Pavel Machek wrote:
> Hi!
> 
> > - 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.

As I said in the other case.  imagine ext2/3 on a a san file system
where 2 systems try to make use of it.  Will they not have issues?

-
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/