From: Christoph Hellwig Subject: Re: [PATCH 7/17] locks: allow {vfs,posix}_lock_file to return conflicting lock Date: Fri, 6 Apr 2007 18:49:07 +0100 Message-ID: <20070406174907.GG32549@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: akpm@osdl.org, Trond Myklebust , Marc Eshel , linux-fsdevel@vger.kernel.org To: "J. Bruce Fields" Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:47957 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2992988AbXDFRtL (ORCPT ); Fri, 6 Apr 2007 13:49:11 -0400 Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Apr 05, 2007 at 07:40:57PM -0400, J. Bruce Fields wrote: > From: Marc Eshel - unquoted > > The nfsv4 protocol's lock operation, in the case of a conflict, returns > information about the conflicting lock. > > It's unclear how clients can use this, so for now we're not going so far as to > add a filesystem method that can return a conflicting lock, but we may as well > return something in the local case when it's easy to. Ok.