linux-kernel - Re: reiser4: maybe just fix bugs?

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

Message-ID: <44D021EE.1040907@slaphack.com>
Date:	Tue, 01 Aug 2006 23:54:22 -0400
From:	David Masover <ninja@...phack.com>
To:	Nate Diller <nate.diller@...il.com>
CC:	"Vladimir V. Saveliev" <vs@...esys.com>,
	Andrew Morton <akpm@...l.org>, vda.linux@...glemail.com,
	linux-kernel@...r.kernel.org, Reiserfs-List@...esys.com
Subject: Re: reiser4: maybe just fix bugs?

Nate Diller wrote:
> On 8/1/06, David Masover <ninja@...phack.com> wrote:
>> Vladimir V. Saveliev wrote:

>> I could be entirely wrong, though.  I speak for neither
>> Hans/Namesys/reiserfs nor LKML.  Talk amongst yourselves...
> 
> i should clarify things a bit here.  yes, hans' goal is for there to
> be no difference between the "xattr" namespace and the "readdir" one.
> unfortunately, this is not feasible with the current VFS, and some
> major work would have to be done to enable this without some
> pathological cases cropping up.  some very smart people think that it
> cannot be done at all.

But an xattr interface should work just fine, even if the rest of the 
system is inaccessible (no readdir interface) -- preventing all these 
pathological problems, except the one where Hans implements it the way 
I'm thinking, and kernel people hate it.
-
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/