From: Chuck Lever <chuck.lever@oracle.com>
To: Olga Kornievskaia <olga.kornievskaia@gmail.com>
Cc: Bruce Fields <bfields@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] NFSD: fix error handling in callbacks
Date: Tue, 9 Mar 2021 17:42:15 +0000 [thread overview]
Message-ID: <63CB3509-0EF2-40F9-88D0-F6AB8FC04DA5@oracle.com> (raw)
In-Reply-To: <CAN-5tyHUWJR6MP-PHc6=26Rz1tO_LYtGmjmU2HFf3uyg4NMXsg@mail.gmail.com>
> On Mar 9, 2021, at 11:46 AM, Olga Kornievskaia <olga.kornievskaia@gmail.com> wrote:
>
> On Tue, Mar 9, 2021 at 11:39 AM Olga Kornievskaia
> <olga.kornievskaia@gmail.com> wrote:
>>
>> On Tue, Mar 9, 2021 at 10:37 AM J. Bruce Fields <bfields@redhat.com> wrote:
>>>
>>> On Tue, Mar 09, 2021 at 09:41:27AM -0500, Olga Kornievskaia wrote:
>>>> From: Olga Kornievskaia <kolga@netapp.com>
>>>>
>>>> When the server tries to do a callback and a client fails it due to
>>>> authentication problems, we need the server to set callback down
>>>> flag in RENEW so that client can recover.
>>>
>>> I was looking at this. It looks to me like this should really be just:
>>>
>>> case 1:
>>> if (task->tk_status)
>>> nfsd4_mark_cb_down(clp, task->tk_status);
>>>
>>> If tk_status showed an error, and the ->done method doesn't return 0 to
>>> tell us it something worth retrying, then the callback failed
>>> permanently, so we should mark the callback path down, regardless of the
>>> exact error.
>>
>> Ok. v2 coming (will change the title to make it 4.0 callback)
>
> Sigh, I didn't change the wording of the commit and left the
> authentication problem which is not accurate enough for this patch (as
> say connection errors are also covered by this patch). Do you need me
> to change the wording of the commit and send v3?
Yes, please post a v3. Thanks.
>>> --b.
>>>
>>>>
>>>> Signed-off-by: Olga Kornievskaia <kolga@netapp.com>
>>>> ---
>>>> fs/nfsd/nfs4callback.c | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/fs/nfsd/nfs4callback.c b/fs/nfsd/nfs4callback.c
>>>> index 052be5bf9ef5..7325592b456e 100644
>>>> --- a/fs/nfsd/nfs4callback.c
>>>> +++ b/fs/nfsd/nfs4callback.c
>>>> @@ -1189,6 +1189,7 @@ static void nfsd4_cb_done(struct rpc_task *task, void *calldata)
>>>> switch (task->tk_status) {
>>>> case -EIO:
>>>> case -ETIMEDOUT:
>>>> + case -EACCES:
>>>> nfsd4_mark_cb_down(clp, task->tk_status);
>>>> }
>>>> break;
>>>> --
>>>> 2.27.0
--
Chuck Lever
next prev parent reply other threads:[~2021-03-09 17:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 14:41 [PATCH 1/1] NFSD: fix error handling in callbacks Olga Kornievskaia
2021-03-09 15:37 ` J. Bruce Fields
2021-03-09 16:39 ` Olga Kornievskaia
2021-03-09 16:46 ` Olga Kornievskaia
2021-03-09 17:42 ` Chuck Lever [this message]
2021-03-09 19:45 ` Scott Mayhew
2021-03-09 20:12 ` J. Bruce Fields
2021-03-09 20:40 ` Scott Mayhew
2021-03-09 20:22 ` Trond Myklebust
2021-03-09 20:41 ` Olga Kornievskaia
2021-03-09 20:59 ` Trond Myklebust
2021-03-10 14:47 ` J. Bruce Fields
2021-03-10 22:09 ` Olga Kornievskaia
2021-03-11 14:58 ` J. Bruce Fields
2021-03-11 15:10 ` Chuck Lever III
2021-03-11 15:16 ` Olga Kornievskaia
2021-03-11 15:18 ` 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=63CB3509-0EF2-40F9-88D0-F6AB8FC04DA5@oracle.com \
--to=chuck.lever@oracle.com \
--cc=bfields@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=olga.kornievskaia@gmail.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).