From: "bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org" <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
To: Ming Chen <mchen-JuQBKiYWLL8cww2/fHdDyodd74u8MsAO@public.gmane.org>
Cc: "linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org"
<trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>,
Erez Zadok
<ezk-2jbElX+0AsP5NRxSJurNR4dd74u8MsAO@public.gmane.org>,
"dhildeb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org"
<dhildeb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
"geoff-6hRICwe+Y+k3uPMLIKxrzw@public.gmane.org"
<geoff-6hRICwe+Y+k3uPMLIKxrzw@public.gmane.org>
Subject: Re: [PATCH] nfsd: consider CLAIM_FH when handing out delegation
Date: Mon, 27 Jan 2014 18:01:31 -0500 [thread overview]
Message-ID: <20140127230131.GB8534@fieldses.org> (raw)
In-Reply-To: <F2EEB2C045C93A4889A2C09F59EDB20858153672-xu12ui6wbl7vS0Fa6ia7EEhEtgXb7Qf/@public.gmane.org>
On Thu, Jan 09, 2014 at 09:26:10PM +0000, Ming Chen wrote:
> CLAIM_FH was added by NFSv4.1. It is the same as CLAIM_NULL except that it
> uses only current FH to identify the file to be opened.
>
> The NFS client is using CLAIM_FH if the FH is available when opening a file.
> Currently, we cannot get any delegation if we stat a file before open it
> because the server delegation code does not recognize CLAIM_FH.
>
> We tested this patch and found delegation can be handed out now when claim is
> CLAIM_FH.
Looks reasonable, thanks; applying.--b.
>
> See http://marc.info/?l=linux-nfs&m=136369847801388&w=2 and
> http://www.linux-nfs.org/wiki/index.php/Server_4.0_and_4.1_issues#New_open_claim_types
>
> Signed-off-by: Ming Chen <mchen-JuQBKiYWLL8cww2/fHdDyodd74u8MsAO@public.gmane.org>
> ---
> fs/nfsd/nfs4state.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index 105d6fa..514d9c2 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -3125,6 +3125,7 @@ nfs4_open_delegation(struct net *net, struct svc_fh *fh,
> goto out_no_deleg;
> break;
> case NFS4_OPEN_CLAIM_NULL:
> + case NFS4_OPEN_CLAIM_FH:
> /*
> * Let's not give out any delegations till everyone's
> * had the chance to reclaim theirs....
> --
> 1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-01-27 23:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 21:26 [PATCH] nfsd: consider CLAIM_FH when handing out delegation Ming Chen
[not found] ` <F2EEB2C045C93A4889A2C09F59EDB20858153672-xu12ui6wbl7vS0Fa6ia7EEhEtgXb7Qf/@public.gmane.org>
2014-01-27 23:01 ` bfields-uC3wQj2KruNg9hUCZPvPmw [this message]
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=20140127230131.GB8534@fieldses.org \
--to=bfields-uc3wqj2krung9huczpvpmw@public.gmane.org \
--cc=dhildeb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=ezk-2jbElX+0AsP5NRxSJurNR4dd74u8MsAO@public.gmane.org \
--cc=geoff-6hRICwe+Y+k3uPMLIKxrzw@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mchen-JuQBKiYWLL8cww2/fHdDyodd74u8MsAO@public.gmane.org \
--cc=trond.myklebust-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org \
/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).