From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Masover Subject: Re: reiser4: maybe just fix bugs? Date: Tue, 01 Aug 2006 23:54:22 -0400 Message-ID: <44D021EE.1040907@slaphack.com> References: <1158166a0607310226m5e134307o8c6bedd1f883479c@mail.gmail.com> <20060801013104.f7557fb1.akpm@osdl.org> <44CEBA0A.3060206@namesys.com> <1154431477.10043.55.camel@tribesman.namesys.com> <20060801073316.ee77036e.akpm@osdl.org> <1154444822.10043.106.camel@tribesman.namesys.com> <44CF879D.1000803@slaphack.com> <5c49b0ed0608011226w328d809fy9d50aa785ad93536@mail.gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <5c49b0ed0608011226w328d809fy9d50aa785ad93536@mail.gmail.com> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Nate Diller Cc: "Vladimir V. Saveliev" , Andrew Morton , vda.linux@googlemail.com, linux-kernel@vger.kernel.org, Reiserfs-List@namesys.com Nate Diller wrote: > On 8/1/06, David Masover 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.