From: Steven Whitehouse <swhiteho@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Peter Staubach <staubach@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org,
Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: [PATCH 6/6] nfs: disable leases over NFS
Date: Fri, 29 Jun 2007 23:30:27 +0100 [thread overview]
Message-ID: <1183156227.3311.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20070629213946.GA4877@fieldses.org>
Hi,
On Fri, 2007-06-29 at 17:39 -0400, J. Bruce Fields wrote:
> On Fri, Jun 29, 2007 at 05:16:19PM -0400, Peter Staubach wrote:
> > First, there is already some support to disable leases for NFS mounted
> > file systems in -mm, I think.
>
> Oops, sorry; my fault for not checking -mm before sending....
>
> > Are you planning on removing it?
>
> I'd rather do that, yes. Any objection?
>
> > Second, it seems to me that EINVAL would be a better error to return
> > than EOPNOTSUPP. This is an invalid operation to apply to this file
> > and might match POSIX style specs better.
>
> I'm not sure what you mean by "might match POSIX style specs better"?
>
> From a quick check, other reasons we'd get EINVAL in this case:
>
> - attempt to get a lease on something other than a regular file.
> - leases disabled with /proc/sys/fs/leases-enable
>
> So if the application calling fcntl knows it was calling it on a regular
> file, then with your proposal an EINVAL return would mean leases were
> disabled for one reason or another, and it could take that as a sign to
> fall back on some other behavior. And I can't see any reason it would
> need to distinguish between those two remaining cases (filesystem
> doesn't support leases, or leases are disabled by the sysctl). So,
> OK, EINVAL sounds fine to me.
>
> But I don't have a really strong opinion. I think the suggestion of
> EOPNOTSUPP was from Steven Whitehouse; Steven, do you care?
>
> --b.
EINVAL is fine by me, just so long as its not EAGAIN then it gets my
blessing :-)
Steve.
next prev parent reply other threads:[~2007-06-29 21:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-29 19:21 vfs lease api J. Bruce Fields
[not found] ` <6e0beaf3e950494a6903571f0b5c9b61fc7bf650.1183143819.git.bfields@citi.umich.edu>
2007-06-29 19:21 ` [PATCH 1/6] locks: share more common lease code J. Bruce Fields
[not found] ` <59343fe9a0b0bdb9c39ed217185b9c0d6c7d8dae.1183143819.git.bfields@citi.umich.edu>
2007-06-29 19:21 ` [PATCH 2/6] locks: provide a file lease method enabling cluster-coherent leases J. Bruce Fields
2007-06-30 9:26 ` Christoph Hellwig
[not found] ` <dc828b771d2a4b78d59bdbe3c583b81887205cab.1183143820.git.bfields@citi.umich.edu>
2007-06-29 19:21 ` [PATCH 3/6] locks: rename lease functions to reflect locks.c conventions J. Bruce Fields
2007-06-30 9:22 ` Christoph Hellwig
2007-07-04 21:42 ` J. Bruce Fields
[not found] ` <b057dca3f8acb125eccdce3a3b84ff04713fea7c.1183143820.git.bfields@citi.umich.edu>
2007-06-29 19:21 ` [PATCH 4/6] locks: fix locks.c lease symbol exports J. Bruce Fields
2007-06-30 9:23 ` Christoph Hellwig
2007-07-04 21:42 ` J. Bruce Fields
[not found] ` <1bdef6b017f0ccb94ed76dbdd2b4cc676e5ef312.1183143820.git.bfields@citi.umich.edu>
2007-06-29 19:21 ` [PATCH 5/6] gfs2: stop giving out non-cluster-coherent leases J. Bruce Fields
2007-06-30 9:27 ` Christoph Hellwig
2007-07-01 15:00 ` J. Bruce Fields
2007-07-04 21:48 ` J. Bruce Fields
2007-06-30 9:20 ` [PATCH 1/6] locks: share more common lease code Christoph Hellwig
2007-07-03 22:17 ` J. Bruce Fields
2007-07-04 8:26 ` Christoph Hellwig
[not found] ` <ce5021881e67029f0e3d6f24109cf2953a0edcd1.1183143820.git.bfields@citi.umich.edu>
2007-06-29 19:21 ` [PATCH 6/6] nfs: disable leases over NFS J. Bruce Fields
2007-06-29 21:16 ` Peter Staubach
2007-06-29 21:39 ` J. Bruce Fields
2007-06-29 22:30 ` Steven Whitehouse [this message]
2007-06-29 22:21 ` J. Bruce Fields
2007-06-30 9:25 ` Christoph Hellwig
2007-07-04 23:22 ` J. Bruce Fields
2007-07-05 15:41 ` J. Bruce Fields
2007-07-11 10:20 ` Christoph Hellwig
2007-07-11 23:10 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1183156227.3311.1.camel@localhost.localdomain \
--to=swhiteho@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=staubach@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).