From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jeff Layton <jlayton@redhat.com>
Cc: Mi Jinlong <mijinlong@cn.fujitsu.com>,
NFSv3 list <linux-nfs@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, ebiederm@xmission.com,
adobriyan@gmail.com, viro@ZenIV.linux.org.uk,
jamie@shareable.org
Subject: Re: [PATCH] VFS: Unlink should revoke all outstanding leases on file
Date: Fri, 14 May 2010 13:17:51 -0400 [thread overview]
Message-ID: <1273857471.4732.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20100514055844.109d2fdc@tlielax.poochiereds.net>
On Fri, 2010-05-14 at 05:58 -0400, Jeff Layton wrote:
> On Fri, 14 May 2010 17:35:27 +0800
> Mi Jinlong <mijinlong@cn.fujitsu.com> wrote:
>
> > After client get one file's READ delegation through NFSv4,
> > server delete this file but don't reclaim the delegation.
> >
> > This patch add break_lease at may_delete, which can reclaim delegations.
> >
> > ---
> > fs/namei.c | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/fs/namei.c b/fs/namei.c
> > index 16df727..17bafc1 100644
> > --- a/fs/namei.c
> > +++ b/fs/namei.c
> > @@ -1338,7 +1338,7 @@ static int may_delete(struct inode *dir,struct dentry *victim,int isdir)
> > return -ENOENT;
> > if (victim->d_flags & DCACHE_NFSFS_RENAMED)
> > return -EBUSY;
> > - return 0;
> > + return break_lease(victim->d_inode, FMODE_WRITE);
> > }
> >
> > /* Check whether we can create an object with dentry child in directory
>
> This doesn't look right to me.
>
> The fcntl(2) manpage basically says that leases should be broken if the
> file is opened for read or write, or is truncated. unlinks don't seem
> to fall into either category...
>
Breaking the lease in this case is certainly a requirement for NFSv4
delegations. I've no idea what the CIFS oplock requirements are...
Cheers
Trond
next prev parent reply other threads:[~2010-05-14 17:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 9:35 [PATCH] VFS: Unlink should revoke all outstanding leases on file Mi Jinlong
2010-05-14 9:35 ` Mi Jinlong
2010-05-14 9:58 ` Jeff Layton
2010-05-14 9:58 ` Jeff Layton
2010-05-14 17:17 ` Trond Myklebust [this message]
2010-05-14 17:38 ` Jeff Layton
2010-05-14 17:38 ` Jeff Layton
2010-05-14 17:46 ` Jamie Lokier
2010-05-14 17:46 ` Jamie Lokier
2010-05-14 18:16 ` Jeremy Allison
2010-05-19 14:06 ` J. Bruce Fields
2010-05-19 16:21 ` Jamie Lokier
2010-05-19 16:21 ` Jamie Lokier
2010-05-14 17:59 ` Trond Myklebust
2010-05-14 17:59 ` Trond Myklebust
2010-05-14 18:31 ` Trond Myklebust
2010-05-14 19:23 ` J. Bruce Fields
2010-05-14 19:23 ` J. Bruce Fields
2010-05-19 9:46 ` Mi Jinlong
2010-05-19 9:46 ` Mi Jinlong
2010-05-19 15:57 ` J. Bruce Fields
2010-05-20 9:46 ` Mi Jinlong
2010-05-20 9:46 ` Mi Jinlong
2010-05-21 21:07 ` J. Bruce Fields
2010-05-21 21:07 ` J. Bruce Fields
2010-05-25 10:14 ` Mi Jinlong
2010-05-25 10:14 ` Mi Jinlong
2010-05-19 16:14 ` Jamie Lokier
2010-05-20 2:21 ` J. Bruce Fields
2010-05-20 2:21 ` J. Bruce Fields
[not found] ` <20100514055844.109d2fdc-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-05-19 9:49 ` Mi Jinlong
2010-05-19 9:49 ` Mi Jinlong
2010-05-19 16:03 ` J. Bruce Fields
2010-05-20 9:23 ` Mi Jinlong
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=1273857471.4732.7.camel@localhost.localdomain \
--to=trond.myklebust@fys.uio.no \
--cc=adobriyan@gmail.com \
--cc=ebiederm@xmission.com \
--cc=jamie@shareable.org \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mijinlong@cn.fujitsu.com \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.