From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: How to handle non-local renames? Date: Thu, 28 Sep 2006 15:20:45 +0100 Message-ID: <20060928142045.GH29920@ftp.linux.org.uk> References: <1158597517.6297.10.camel@lade.trondhjem.org> <1158883241.5535.7.camel@lade.trondhjem.org> <20060928100223.GY29920@ftp.linux.org.uk> <1159446678.5439.23.camel@lade.trondhjem.org> <20060928124247.GD29920@ftp.linux.org.uk> <1159448228.5439.26.camel@lade.trondhjem.org> <20060928131545.GF29920@ftp.linux.org.uk> <1159450319.5439.44.camel@lade.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Miklos Szeredi , dhowells@redhat.com, linux-fsdevel@vger.kernel.org Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:16324 "EHLO ZenIV.linux.org.uk") by vger.kernel.org with ESMTP id S1161145AbWI1OUr (ORCPT ); Thu, 28 Sep 2006 10:20:47 -0400 To: Trond Myklebust Content-Disposition: inline In-Reply-To: <1159450319.5439.44.camel@lade.trondhjem.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Sep 28, 2006 at 09:31:59AM -0400, Trond Myklebust wrote: > Furthermore, it would upset a lot of people to change the current > behaviour which does support remote rename, and has supported it for the > past 10 years at least. I'd therefore prefer to go for a workaround that > addresses the problem of the deadlocks instead of the useful > functionality. OK... I'll look into your variant again when I get some sleep - I'm afraid that there are remaining holes, but right now I'm not in any condition to verify that (or prove that there's none)... Later tonight...