Return-Path: linux-nfs-owner@vger.kernel.org Received: from bombadil.infradead.org ([198.137.202.9]:39984 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754912AbaFWQMz (ORCPT ); Mon, 23 Jun 2014 12:12:55 -0400 Date: Mon, 23 Jun 2014 09:12:54 -0700 From: Christoph Hellwig To: Jeff Layton Cc: bfields@fieldses.org, linux-nfs@vger.kernel.org Subject: Re: [PATCH v1 009/104] locks: add file_has_lease Message-ID: <20140623161254.GG24193@infradead.org> References: <1403189450-18729-1-git-send-email-jlayton@primarydata.com> <1403189450-18729-10-git-send-email-jlayton@primarydata.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1403189450-18729-10-git-send-email-jlayton@primarydata.com> Sender: linux-nfs-owner@vger.kernel.org List-ID: On Thu, Jun 19, 2014 at 10:49:15AM -0400, Jeff Layton wrote: > Add a function that can tell us whether a file description has had a > lease set on it. The code looks good, but how is this information useful given that it will be stable as soon as i_lock is dropped?