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. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
