From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Dave Wysochanski <dwysocha@redhat.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] nfsd4: Expose the callback address and state of each NFS4 client
Date: Wed, 26 May 2021 14:30:11 -0400 [thread overview]
Message-ID: <20210526183011.GA7823@fieldses.org> (raw)
In-Reply-To: <6C2F8C95-E29F-4BB3-9127-6ED5D825ACB7@oracle.com>
On Tue, May 25, 2021 at 09:48:38PM +0000, Chuck Lever III wrote:
>
>
> > On May 25, 2021, at 4:58 PM, Bruce Fields <bfields@fieldses.org> wrote:
> >
> > When I run trace-cmd report I get output like:
> >
> > [nfsd:nfsd_cb_state] function cb_state2str not defined
> > [nfsd:nfsd_cb_shutdown] function cb_state2str not defined
> > [nfsd:nfsd_cb_probe] function cb_state2str not defined
> > [nfsd:nfsd_cb_lost] function cb_state2str not defined
> >
> > I don't know how this is supposed to work. Is it OK for tracepoint definitions
> > to reference kernel functions if they're defined in the right way somehow? If
> > not, I don't know what the solution would be for sharing this--define a macro
> > that expands to the array literal and use that in both places? Or maybe just
> > live with the the redundancy.
>
> Living with the redundancy is OK with me.
OK, I'll revert back to Dave's first version of this patch.
--b.
diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
index 49c052243b5c..89a7cada334d 100644
--- a/fs/nfsd/nfs4state.c
+++ b/fs/nfsd/nfs4state.c
@@ -2357,6 +2357,21 @@ static void seq_quote_mem(struct seq_file *m, char *data, int len)
seq_printf(m, "\"");
}
+static const char *cb_state_str(int state)
+{
+ switch (state) {
+ case NFSD4_CB_UP:
+ return "UP";
+ case NFSD4_CB_UNKNOWN:
+ return "UNKNOWN";
+ case NFSD4_CB_DOWN:
+ return "DOWN";
+ case NFSD4_CB_FAULT:
+ return "FAULT";
+ }
+ return "UNDEFINED";
+}
+
static int client_info_show(struct seq_file *m, void *v)
{
struct inode *inode = m->private;
@@ -2385,6 +2400,8 @@ static int client_info_show(struct seq_file *m, void *v)
seq_printf(m, "\nImplementation time: [%lld, %ld]\n",
clp->cl_nii_time.tv_sec, clp->cl_nii_time.tv_nsec);
}
+ seq_printf(m, "callback state: %s\n", cb_state_str(clp->cl_cb_state));
+ seq_printf(m, "callback address: %pISpc\n", &clp->cl_cb_conn.cb_addr);
drop_client(clp);
return 0;
--
1.8.3.1
next prev parent reply other threads:[~2021-05-26 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 20:29 [PATCH v2 0/1] Add callback address and state to nfsd4 client info Dave Wysochanski
2021-05-17 20:29 ` [PATCH v2 1/1] nfsd4: Expose the callback address and state of each NFS4 client Dave Wysochanski
2021-05-25 20:58 ` Bruce Fields
2021-05-25 21:48 ` Chuck Lever III
2021-05-26 18:30 ` Bruce Fields [this message]
2021-05-26 19:13 ` David Wysochanski
2021-05-26 1:32 ` Trond Myklebust
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=20210526183011.GA7823@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=dwysocha@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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