From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: linux-nfs@vger.kernel.org, lorenzo.bianconi@redhat.com,
chuck.lever@oracle.com
Subject: Re: [PATCH v2] NFSD: add rpc_status entry in nfsd debug filesystem
Date: Fri, 14 Jul 2023 19:01:33 +0200 [thread overview]
Message-ID: <ZLF/bedAa57iys+q@lore-desk> (raw)
In-Reply-To: <d0b5e760aebaff9a587a83c7d69f71a5d71f01e6.camel@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 3056 bytes --]
[...]
> > + if (rqstp->rq_addr.ss_family == AF_INET)
> > + seq_printf(m, " %pI4 %pI4 ",
> > + &((struct sockaddr_in *)&rqstp->rq_addr)->sin_addr,
> > + &((struct sockaddr_in *)&rqstp->rq_daddr)->sin_addr);
> > + else if (rqstp->rq_addr.ss_family == AF_INET6)
> > + seq_printf(m, " %pI6 %pI6 ",
> > + &((struct sockaddr_in6 *)&rqstp->rq_addr)->sin6_addr,
> > + &((struct sockaddr_in6 *)&rqstp->rq_daddr)->sin6_addr);
> > + else
> > + seq_printf(m, " unknown:%hu",
>
> I think you'll need to add a second "unknown:%hu" here to keep the
> fields aligned. In the ipv4/6 case there are 2 addresses, so you need 2
> addresses here as well.
ack, I will fix it.
>
> > + rqstp->rq_addr.ss_family);
> > +#ifdef CONFIG_NFSD_V4
> > + if (rqstp->rq_vers == NFS4_VERSION &&
> > + rqstp->rq_proc == NFSPROC4_COMPOUND) {
> > + /* NFSv4 compund */
> > + struct nfsd4_compoundargs *args = rqstp->rq_argp;
> > + struct nfsd4_compoundres *resp = rqstp->rq_resp;
> > +
> > + while (resp->opcnt < args->opcnt) {
> > + struct nfsd4_op *op = &args->ops[resp->opcnt++];
> > +
> > + seq_printf(m, " %s", nfsd4_op_name(op->opnum));
>
> Given that this is going to be a variable-length field, we should have a
> different delimiter between the different operations here. Maybe
> something like a ':' or '|' character? That way the script could parse
> the different operations, but we'd still be able to add new fields to
> the end of the line later if we decide it's worthwhile.
ack, I will fix it.
Regards,
Lorenzo
>
> > + }
> > + }
> > +#endif /* CONFIG_NFSD_V4 */
> > + seq_puts(m, "\n");
> > + }
> > + }
> > +
> > + rcu_read_unlock();
> > +
> > + return 0;
> > +}
> > +
> > +/**
> > + * nfsd_rpc_status_open - Atomically copy a write verifier
> > + * @inode: entry inode pointer.
> > + * @file: entry file pointer.
> > + *
> > + * This routine dumps pending RPC requests info queued into nfs server.
> > + */
> > +int nfsd_rpc_status_open(struct inode *inode, struct file *file)
> > +{
> > + struct nfsd_net *nn = net_generic(inode->i_sb->s_fs_info, nfsd_net_id);
> > +
> > + mutex_lock(&nfsd_mutex);
> > + if (!nn->nfsd_serv) {
> > + mutex_unlock(&nfsd_mutex);
> > + return -ENODEV;
> > + }
> > +
> > + svc_get(nn->nfsd_serv);
> > + mutex_unlock(&nfsd_mutex);
> > +
> > + return single_open(file, nfsd_rpc_status_show, inode->i_private);
> > +}
> > diff --git a/net/sunrpc/svc.c b/net/sunrpc/svc.c
> > index 587811a002c9..44eac83b35a1 100644
> > --- a/net/sunrpc/svc.c
> > +++ b/net/sunrpc/svc.c
> > @@ -1629,7 +1629,7 @@ const char *svc_proc_name(const struct svc_rqst *rqstp)
> > return rqstp->rq_procinfo->pc_name;
> > return "unknown";
> > }
> > -
> > +EXPORT_SYMBOL_GPL(svc_proc_name);
> >
> > /**
> > * svc_encode_result_payload - mark a range of bytes as a result payload
>
> Other than the nits above, this is looking good!
> --
> Jeff Layton <jlayton@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-07-14 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 21:44 [PATCH v2] NFSD: add rpc_status entry in nfsd debug filesystem Lorenzo Bianconi
2023-07-13 11:27 ` Jeff Layton
2023-07-14 17:01 ` Lorenzo Bianconi [this message]
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=ZLF/bedAa57iys+q@lore-desk \
--to=lorenzo@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.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).