From: Jeff Layton <jlayton@kernel.org>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: Chuck Lever <chuck.lever@oracle.com>, Neil Brown <neilb@suse.de>,
Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] nfsd: add more info to WARN_ON_ONCE on failed callbacks
Date: Thu, 19 Dec 2024 16:33:10 -0500 [thread overview]
Message-ID: <4ea104be11ae3979e76144d3018ede5e0d49cc3c.camel@kernel.org> (raw)
In-Reply-To: <CAN-5tyGWmAZ2ovmS4SqiEoZhokxOG+ERvOVFB6ziTqE-ahLFUg@mail.gmail.com>
On Thu, 2024-12-19 at 16:23 -0500, Olga Kornievskaia wrote:
> On Mon, Aug 26, 2024 at 8:54 AM Jeff Layton <jlayton@kernel.org> wrote:
> >
> > Currently, you get the warning and stack trace, but nothing is printed
> > about the relevant error codes. Add that in.
> >
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > fs/nfsd/nfs4callback.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/fs/nfsd/nfs4callback.c b/fs/nfsd/nfs4callback.c
> > index d756f443fc44..dee9477cc5b5 100644
> > --- a/fs/nfsd/nfs4callback.c
> > +++ b/fs/nfsd/nfs4callback.c
> > @@ -1333,7 +1333,8 @@ static void nfsd4_cb_done(struct rpc_task *task, void *calldata)
> > return;
> >
> > if (cb->cb_status) {
> > - WARN_ON_ONCE(task->tk_status);
> > + WARN_ONCE(task->tk_status, "cb_status=%d tk_status=%d",
> > + cb->cb_status, task->tk_status);
>
> Can we add cb->cb_ops->opcode to that as well?
I'd be fine with that, but this patch is already merged. Care to
propose one that could go on top?
>
> > task->tk_status = cb->cb_status;
> > }
> >
> >
> > --
> > 2.46.0
> >
> >
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2024-12-19 21:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 12:50 [PATCH 0/3] nfsd: callback debugging improvements Jeff Layton
2024-08-26 12:50 ` [PATCH 1/3] nfsd: add more info to WARN_ON_ONCE on failed callbacks Jeff Layton
2024-09-09 17:23 ` Olga Kornievskaia
2024-09-09 17:34 ` Jeff Layton
2024-12-19 21:23 ` Olga Kornievskaia
2024-12-19 21:33 ` Jeff Layton [this message]
2024-12-19 21:42 ` Olga Kornievskaia
2024-08-26 12:50 ` [PATCH 2/3] nfsd: track the main opcode for callbacks Jeff Layton
2024-08-26 12:50 ` [PATCH 3/3] nfsd: add more nfsd_cb tracepoints Jeff Layton
2024-08-26 16:34 ` [PATCH 0/3] nfsd: callback debugging improvements Chuck Lever
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=4ea104be11ae3979e76144d3018ede5e0d49cc3c.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=aglo@umich.edu \
--cc=chuck.lever@oracle.com \
--cc=kolga@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tom@talpey.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