From: dai.ngo@oracle.com
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Bruce Fields <bfields@fieldses.org>,
Jeff Layton <jlayton@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH RFC v15 04/11] NFSD: Update nfsd_breaker_owns_lease() to handle courtesy clients
Date: Wed, 9 Mar 2022 21:09:17 -0800 [thread overview]
Message-ID: <efc9edcf-d6ce-e0a1-d00d-e31f6287d6d3@oracle.com> (raw)
In-Reply-To: <541790B3-6B92-4A85-8756-04615222EFF4@oracle.com>
On 3/9/22 1:46 PM, Chuck Lever III wrote:
>
>> On Mar 4, 2022, at 7:37 PM, Dai Ngo <dai.ngo@oracle.com> wrote:
>>
>> Update nfsd_breaker_owns_lease() to handle delegation conflict
>> with courtesy clients. If conflict was caused courtesy client
>> then discard the courtesy client by setting CLIENT_EXPIRED and
>> return conflict resolved. Client with CLIENT_EXPIRED is expired
>> by the laundromat.
>>
>> Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
>> ---
>> fs/nfsd/nfs4state.c | 18 ++++++++++++++++++
>> 1 file changed, 18 insertions(+)
>>
>> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
>> index 583ac807e98d..40a357fd1a14 100644
>> --- a/fs/nfsd/nfs4state.c
>> +++ b/fs/nfsd/nfs4state.c
>> @@ -4727,6 +4727,24 @@ static bool nfsd_breaker_owns_lease(struct file_lock *fl)
>> struct svc_rqst *rqst;
>> struct nfs4_client *clp;
>>
>> + clp = dl->dl_stid.sc_client;
>> + /*
>> + * need to sync with courtesy client trying to reconnect using
>> + * the cl_cs_lock, nn->client_lock can not be used since this
>> + * function is called with the fl_lck held.
>> + */
>> + spin_lock(&clp->cl_cs_lock);
>> + if (test_bit(NFSD4_CLIENT_EXPIRED, &clp->cl_flags)) {
>> + spin_unlock(&clp->cl_cs_lock);
>> + return true;
>> + }
>> + if (test_bit(NFSD4_CLIENT_COURTESY, &clp->cl_flags)) {
>> + set_bit(NFSD4_CLIENT_EXPIRED, &clp->cl_flags);
>> + spin_unlock(&clp->cl_cs_lock);
>> + return true;
>> + }
>> + spin_unlock(&clp->cl_cs_lock);
>> +
> Nit: Please add nfs4_check_and_expire_courtesy_client() in this patch
> instead of in 05/11.
That means nfs4_check_and_expire_courtesy_client is being called
in 05/11 but is not defined in 05/11. Is that ok?
-Dai
>
>
>> if (!i_am_nfsd())
>> return false;
>> rqst = kthread_data(current);
>> --
>> 2.9.5
>>
> --
> Chuck Lever
>
>
>
next prev parent reply other threads:[~2022-03-10 5:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 0:37 [PATCH RFC v15 0/11] NFSD: Initial implementation of NFSv4 Courteous Server Dai Ngo
2022-03-05 0:37 ` [PATCH RFC v15 01/11] fs/lock: add helper locks_any_blockers to check for blockers Dai Ngo
2022-03-09 20:56 ` Chuck Lever III
2022-03-10 3:11 ` dai.ngo
2022-03-10 4:08 ` Chuck Lever III
2022-03-10 4:45 ` dai.ngo
2022-03-05 0:37 ` [PATCH RFC v15 02/11] NFSD: Add client flags, macro and spinlock to support courteous server Dai Ngo
2022-03-05 0:37 ` [PATCH RFC v15 03/11] NFSD: Add lm_lock_expired call out Dai Ngo
2022-03-05 0:37 ` [PATCH RFC v15 04/11] NFSD: Update nfsd_breaker_owns_lease() to handle courtesy clients Dai Ngo
2022-03-09 21:46 ` Chuck Lever III
2022-03-10 5:09 ` dai.ngo [this message]
2022-03-10 14:02 ` Chuck Lever III
2022-03-05 0:37 ` [PATCH RFC v15 05/11] NFSD: Update nfs4_get_vfs_file() " Dai Ngo
2022-03-05 0:37 ` [PATCH RFC v15 06/11] NFSD: Update find_clp_in_name_tree() " Dai Ngo
2022-03-09 22:08 ` Chuck Lever III
2022-03-10 3:11 ` dai.ngo
2022-03-05 0:37 ` [PATCH RFC v15 07/11] NFSD: Update find_in_sessionid_hashtbl() " Dai Ngo
2022-03-09 22:42 ` Chuck Lever III
2022-03-10 3:12 ` dai.ngo
2022-03-10 3:33 ` Chuck Lever III
2022-03-10 4:43 ` dai.ngo
2022-03-05 0:37 ` [PATCH RFC v15 08/11] NFSD: Update find_client_in_id_table() " Dai Ngo
2022-03-05 0:37 ` [PATCH RFC v15 09/11] NFSD: Refactor nfsd4_laundromat() Dai Ngo
2022-03-05 0:37 ` [PATCH RFC v15 10/11] NFSD: Update laundromat to handle courtesy clients Dai Ngo
2022-03-05 0:37 ` [PATCH RFC v15 11/11] NFSD: Show state of courtesy clients in client info Dai Ngo
2022-03-09 20:14 ` Chuck Lever III
2022-03-09 20:51 ` dai.ngo
2022-03-10 3:09 ` dai.ngo
2022-03-10 3:27 ` Chuck Lever III
2022-03-10 15:00 ` Bruce Fields
2022-03-10 17:59 ` dai.ngo
2022-03-10 14:43 ` Chuck Lever III
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=efc9edcf-d6ce-e0a1-d00d-e31f6287d6d3@oracle.com \
--to=dai.ngo@oracle.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--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 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).