Return-Path: linux-nfs-owner@vger.kernel.org Received: from bombadil.infradead.org ([198.137.202.9]:51908 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755210AbaIDUMA (ORCPT ); Thu, 4 Sep 2014 16:12:00 -0400 Date: Thu, 4 Sep 2014 13:12:00 -0700 From: Christoph Hellwig To: Trond Myklebust Cc: Jeff Layton , Devel FS Linux , Linux NFS Mailing List , Christoph Hellwig , "J. Bruce Fields" , Linux Kernel mailing list , Steven Whitehouse , cluster-devel Subject: Re: [PATCH v2 01/17] locks: consolidate "nolease" routines Message-ID: <20140904201200.GA26054@infradead.org> References: <1409834323-7171-1-git-send-email-jlayton@primarydata.com> <1409834323-7171-2-git-send-email-jlayton@primarydata.com> <20140904084938.2664bf0a@tlielax.poochiereds.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-nfs-owner@vger.kernel.org List-ID: On Thu, Sep 04, 2014 at 02:25:35PM -0400, Trond Myklebust wrote: > Actually, it looks as if when you compile with !CONFIG_FILE_LOCKING, > then fcntl_setlease() returns the value '0' (which would be > "success!"). The word "confusing" only begins to describe it all. That's incorrect for sure, we should agree on a single sensible code for: 1) !CONFIG_FILE_LOCKING 2) !lease_enable 3) filesystem doesn't support leases.