Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 18 Nov 2002 19:58:20 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 18 Nov 2002 19:58:20 -0500 Received: from patan.Sun.COM ([192.18.98.43]:11413 "EHLO patan.sun.com") by vger.kernel.org with ESMTP id ; Mon, 18 Nov 2002 19:58:19 -0500 Message-Id: <200211190104.gAJ14Wf9136218@athyra.eng.sun.com> From: mike.kupfer@sun.com To: trond.myklebust@fys.uio.no cc: Juan Gomez , linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net Subject: Re: [NFS] Re: Non-blocking lock requests during the grace period In-Reply-To: Your message of "Fri, 15 Nov 2002 21:01:21 +0100." <15829.21137.152716.652146@helicity.uio.no> Mime-Version: 1.0 (generated by tm-edit 1.8) Content-Type: text/plain; charset=US-ASCII Date: Mon, 18 Nov 2002 17:04:32 -0800 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1058 Lines: 27 >>>>> "Trond" == Trond Myklebust writes: >>>>> " " == Juan Gomez writes: >> (note that F_GETLK man page does not provide EAGAIN as a >> possible error code). F_GETLK indicates a conflict by changing the arg struct to show the conflicting lock. As for the original topic, I would hesitate before changing the client locking code to return EAGAIN just because the server is in its grace period. The "blocking" or "non-blocking" behavior is tied to what happens when there is already a lock that conflicts with the requested one. When the server is in the grace period, it's unknown as to whether there is already a lock that conflicts with the requested one. Mike Kupfer mike.kupfer@sun.com Solaris File Sharing Speaking for myself, not for Sun. - 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/