From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 3/6] leases: break read leases on unlink Date: Wed, 21 Sep 2011 11:02:41 -0400 Message-ID: <20110921150241.GA11452@infradead.org> References: <1316617097-21384-1-git-send-email-bfields@redhat.com> <1316617097-21384-4-git-send-email-bfields@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, samba-technical-w/Ol4Ecudpl8XjKLYN78aQ@public.gmane.org, Christoph Hellwig , Al Viro , Mimi Zohar To: "J. Bruce Fields" Return-path: Content-Disposition: inline In-Reply-To: <1316617097-21384-4-git-send-email-bfields-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Sep 21, 2011 at 10:58:14AM -0400, J. Bruce Fields wrote: > A read lease is used by NFSv4 as a guarantee that a client can perform > local read opens without informing the server. > > The open operation takes the last component of the pathname as an > argument, thus is also a lookup operation, and giving the client the > above guarantee means informing the client before we allow anything that > would change the set of names pointing to the inode. That seems like totally strange semantics. A useful defintion of a lase operation would mean it guarantees I/O can happen, and wouldn't care about metadata operation. That's the whole point in adding a stateful open to nfs4, isn't it? -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html