Re: [nfsv4] "Courtesy locks"

"J. Bruce Fields" <bfields@fieldses.org> Mon, 13 September 2010 17:17 UTC

Return-Path: <bfields@fieldses.org>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 980C93A6A1E for <nfsv4@core3.amsl.com>; Mon, 13 Sep 2010 10:17:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMu2u85dj92G for <nfsv4@core3.amsl.com>; Mon, 13 Sep 2010 10:17:29 -0700 (PDT)
Received: from fieldses.org (fieldses.org [174.143.236.118]) by core3.amsl.com (Postfix) with ESMTP id 4F9CD3A693E for <nfsv4@ietf.org>; Mon, 13 Sep 2010 10:17:26 -0700 (PDT)
Received: from bfields by fieldses.org with local (Exim 4.71) (envelope-from <bfields@fieldses.org>) id 1OvCe9-0004Fc-MI; Mon, 13 Sep 2010 13:16:49 -0400
Date: Mon, 13 Sep 2010 13:16:49 -0400
To: david.noveck@emc.com
Message-ID: <20100913171649.GA16253@fieldses.org>
References: <BF3BB6D12298F54B89C8DCC1E4073D8002665106@CORPUSMX50A.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <BF3BB6D12298F54B89C8DCC1E4073D8002665106@CORPUSMX50A.corp.emc.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
From: "J. Bruce Fields" <bfields@fieldses.org>
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] "Courtesy locks"
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Sep 2010 17:17:31 -0000

On Sun, Sep 12, 2010 at 12:21:43PM -0400, david.noveck@emc.com wrote:
> The term "courtesy locks" is Trond's.  It refers to the practice of
> allowing locks associated with an expired lease to remain around, "as a
> courtesy to the client or as an optimization" (see section 8.6.3 or RFC
> 3530).  The text that is associated with this situation is not as clear
> or complete as it should be and a number of RFC3530bis issues are
> related to it.
> 
> In deciding how to address this, we need to find out what exactly
> clients and servers do.  A long while back I promised to send mail and
> gather up the requisite information, and now my promise has caught up
> with me.  If you can answer the following questions via email that would
> be great.  If not, I hope people will at least find out what their
> implementations do on these points so we discuss it at the upcoming
> bakeathon.
> 
> This looks pretty daunting but most people will probably say "Yes" to
> (S1) and/or easily deal with (C1), (C2), and (C3).
> 
> Make sure you use black pen and completely fill in the circles :-) 
> 
> 
> If you have a client and not a server, skip to (C1)

Talking about the Linux server:

> S1) When a lease expires, do you simply release all
>     the associated locks?

Yes.

>     If so, go to (C1), or if you don't have a client you 
>     are all done.

That was easy!

--b.