Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 30 Jul 2001 13:37:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 30 Jul 2001 13:37:37 -0400 Received: from weta.f00f.org ([203.167.249.89]:26502 "HELO weta.f00f.org") by vger.kernel.org with SMTP id ; Mon, 30 Jul 2001 13:37:34 -0400 Date: Tue, 31 Jul 2001 05:38:13 +1200 From: Chris Wedgwood To: Rik van Riel Cc: Lawrence Greenfield , "Patrick J. LoPresti" , linux-kernel@vger.kernel.org, Alan Cox , Chris Mason Subject: Re: ext3-2.4-0.9.4 Message-ID: <20010731053813.A5961@weta.f00f.org> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i X-No-Archive: Yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Original-Recipient: rfc822;linux-kernel-outgoing On Mon, Jul 30, 2001 at 02:25:51PM -0300, Rik van Riel wrote: Note that this is very different from the "link() should be synchronous()" mantra we've been hearing over the last days. These fsync() semantics make lots of sense to me, I'm all for it. And what if the file has hundreds or thousands of links? How do we cleanly keep track of all those? --cw - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/