linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 07/11] NFSD: Update find_in_sessionid_hashtbl() to handle courtesy clients
Date: Wed, 9 Mar 2022 20:43:51 -0800	[thread overview]
Message-ID: <2362ce2b-ae2e-2399-d43b-f3473313bb0c@oracle.com> (raw)
In-Reply-To: <CDA6815A-D05A-4DE1-B065-4398ACF8AEF0@oracle.com>


On 3/9/22 7:33 PM, Chuck Lever III wrote:
>> On Mar 9, 2022, at 10:12 PM, Dai Ngo <dai.ngo@oracle.com> wrote:
>>
>> 
>>> On 3/9/22 2:42 PM, Chuck Lever III wrote:
>>>
>>>>> On Mar 4, 2022, at 7:37 PM, Dai Ngo <dai.ngo@oracle.com> wrote:
>>>> Update find_in_sessionid_hashtbl to:
>>>> . skip client with CLIENT_EXPIRED flag; discarded courtesy client.
>>>> . if courtesy client was found then clear CLIENT_COURTESY and
>>>>    set CLIENT_RECONNECTED so callers can take appropriate action.
>>>>
>>>> Update nfsd4_sequence and nfsd4_bind_conn_to_session to create client
>>>> record for client with CLIENT_RECONNECTED set.
>>>>
>>>> Update nfsd4_destroy_session to discard client with CLIENT_RECONNECTED
>>>> set.
>>>>
>>>> Signed-off-by: Dai Ngo <dai.ngo@oracle.com>
>>>> ---
>>>> fs/nfsd/nfs4state.c | 34 ++++++++++++++++++++++++++++++++--
>>>> 1 file changed, 32 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
>>>> index f42d72a8f5ca..34a59c6f446c 100644
>>>> --- a/fs/nfsd/nfs4state.c
>>>> +++ b/fs/nfsd/nfs4state.c
>>>> @@ -1963,13 +1963,22 @@ find_in_sessionid_hashtbl(struct nfs4_sessionid *sessionid, struct net *net,
>>>> {
>>>>     struct nfsd4_session *session;
>>>>     __be32 status = nfserr_badsession;
>>>> +    struct nfs4_client *clp;
>>>>
>>>>     session = __find_in_sessionid_hashtbl(sessionid, net);
>>>>     if (!session)
>>>>         goto out;
>>>> +    clp = session->se_client;
>>>> +    if (clp && nfs4_is_courtesy_client_expired(clp)) {
>>>> +        session = NULL;
>>>> +        goto out;
>>>> +    }
>>>>     status = nfsd4_get_session_locked(session);
>>>> -    if (status)
>>>> +    if (status) {
>>>>         session = NULL;
>>>> +        if (clp && test_bit(NFSD4_CLIENT_COURTESY, &clp->cl_flags))
> By the way, I don’t understand why this checks CLIENT_COURTESY to see if the clp should be discarded. Shouldn’t it check CLIENT_RECONNECTED like the other sites?

Thanks, this should check for CLIENT_RECONNECTED as described
in the commit message.

>
>
>>>> +            nfsd4_discard_courtesy_clnt(clp);
>>>> +    }
>>> Here and above: I'm not seeing how @clp can be NULL, but I'm kind
>>> of new to fs/nfsd/nfs4state.c.
>> it seems like @clp can not be NULL since existing code does not
>> check for it. I will remove it to avoid any confusion. Can this
>> be done as a separate clean up patch?
> I don’t think this series is going to make v5.18. We can keep working on improving each of the patches. And I would rather ensure that the series is properly bisectable. I don’t think we’re at a point where the patches are immutable.

okay, I will submit v16 to address review comments.

-Dai


  reply	other threads:[~2022-03-10  4:44 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
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 [this message]
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=2362ce2b-ae2e-2399-d43b-f3473313bb0c@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).