From: Scott Mayhew <smayhew@redhat.com>
To: "J. Bruce Fields" <bfields@redhat.com>
Cc: Olga Kornievskaia <olga.kornievskaia@gmail.com>,
chuck.lever@oracle.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/1] NFSD: fix error handling in callbacks
Date: Tue, 9 Mar 2021 14:45:19 -0500 [thread overview]
Message-ID: <20210309194519.GF2597609@aion.usersys.redhat.com> (raw)
In-Reply-To: <YEeWK+gs4c8O7k0u@pick.fieldses.org>
On Tue, 09 Mar 2021, J. Bruce Fields 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.
That switch was added because the server was erroneously setting
SEQ4_STATUS_CB_PATH_DOWN in the event that a client returned an
NFS-level error for a CB_RECALL that the client had already done a
FREE_STATEID for. Removing the switch will cause the server to go back
to that behaviour, won't it?
-Scott
>
> --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
> >
>
next prev parent reply other threads:[~2021-03-09 19:46 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
2021-03-09 19:45 ` Scott Mayhew [this message]
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=20210309194519.GF2597609@aion.usersys.redhat.com \
--to=smayhew@redhat.com \
--cc=bfields@redhat.com \
--cc=chuck.lever@oracle.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).