From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: silent semantic changes with reiser4 Date: Mon, 30 Aug 2004 00:42:13 -0700 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <4132DA55.5080903@namesys.com> References: <412F7D63.4000109@namesys.com> <20040827230857.69340aec.pj@sgi.com> <20040829150231.GE9471@alias> <4132205A.9080505@namesys.com> <20040829183629.GP21964@parcelfarce.linux.theplanet.co.uk> <20040829185744.GQ21964@parcelfarce.linux.theplanet.co.uk> <41323751.5000607@namesys.com> <20040829212700.GA16297@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: flx@msu.ru, Paul Jackson , riel@redhat.com, ninja@slaphack.com, torvalds@osdl.org, diegocg@teleline.es, jamie@shareable.org, christophe@saout.de, vda@port.imtp.ilyichevsk.odessa.ua, christer@weinigel.se, spam@tnonline.net, akpm@osdl.org, wichert@wiggy.net, jra@samba.org, hch@lst.de, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, flx@namesys.com, reiserfs-list@namesys.com Return-path: Received: from rwcrmhc12.comcast.net ([216.148.227.85]:39421 "EHLO rwcrmhc12.comcast.net") by vger.kernel.org with ESMTP id S266879AbUH3HrV (ORCPT ); Mon, 30 Aug 2004 03:47:21 -0400 To: viro@parcelfarce.linux.theplanet.co.uk In-Reply-To: <20040829212700.GA16297@parcelfarce.linux.theplanet.co.uk> List-Id: linux-fsdevel.vger.kernel.org I think we have to either: 1) Link only to the file and not the directory in the file-directory duality. This means we change the semantics of hard link so that it only links to the data and the standard metadata, and the optional attributes/streams/files-in-directory are not seen by the second link. You can think of this as meaning that hard links only connect to the file and not the directory in the file-directory wave-particle duality or, 2) we should ask Alexander Smith to help with applying the graph traversal cycle detection code that he wrote. I can go either way contentedly for now. 2) is the right long term solution. 1) is probably the right short term solution. Ok, Linus and Viro, now I see why it was hard. Being able to effectively connect to compound documents only with symlinks is a bit distasteful, but it is quite livable, and I very much hope you decide it is better than fragmenting the namespace. Hans