Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"chuck.lever@oracle.com" <chuck.lever@oracle.com>
Subject: Re: [PATCH v2 2/2] SUNRPC: Fix the svc_deferred_event trace class
Date: Wed, 6 Apr 2022 20:34:58 +0000	[thread overview]
Message-ID: <7976abc7a7ea7bbc445256884d0164a1b3ac5bb6.camel@hammerspace.com> (raw)
In-Reply-To: <164926848846.12216.6872977249610829189.stgit@klimt.1015granger.net>

On Wed, 2022-04-06 at 14:08 -0400, Chuck Lever wrote:
> Fix a NULL deref crash that occurs when an svc_rqst is deferred
> while the sunrpc tracing subsystem is enabled. svc_revisit() sets
> dr->xprt to NULL, so it can't be relied upon in the tracepoint to
> provide the remote's address.
> 
> Since __sockaddr() and friends are not available before v5.18, this
> is just a partial revert of commit ece200ddd54b ("sunrpc: Save
> remote presentation address in svc_xprt for trace events") in order
> to enable backports of the fix. It can be cleaned up during a
> future merge window.
> 
> Fixes: ece200ddd54b ("sunrpc: Save remote presentation address in
> svc_xprt for trace events")
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>  include/trace/events/sunrpc.h |    9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/include/trace/events/sunrpc.h
> b/include/trace/events/sunrpc.h
> index ab8ae1f6ba84..4abc2fddd3b8 100644
> --- a/include/trace/events/sunrpc.h
> +++ b/include/trace/events/sunrpc.h
> @@ -2017,18 +2017,19 @@ DECLARE_EVENT_CLASS(svc_deferred_event,
>         TP_STRUCT__entry(
>                 __field(const void *, dr)
>                 __field(u32, xid)
> -               __string(addr, dr->xprt->xpt_remotebuf)
> +               __dynamic_array(u8, addr, dr->addrlen)
>         ),
>  
>         TP_fast_assign(
>                 __entry->dr = dr;
>                 __entry->xid = be32_to_cpu(*(__be32 *)(dr->args +
>                                                        (dr-
> >xprt_hlen>>2)));
> -               __assign_str(addr, dr->xprt->xpt_remotebuf);
> +               memcpy(__get_dynamic_array(addr), &dr->addr, dr-
> >addrlen);
>         ),
>  
> -       TP_printk("addr=%s dr=%p xid=0x%08x", __get_str(addr),
> __entry->dr,
> -               __entry->xid)
> +       TP_printk("addr=%pISpc dr=%p xid=0x%08x",
> +               (struct sockaddr *)__get_dynamic_array(addr),
> +               __entry->dr, __entry->xid)
>  );
> 

Have you tested this? I found myself hitting the warning

"event %s has unsafe dereference of argument %d"

in test_event_printk() when I tried to use something similar for the
NFS code.

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2022-04-06 21:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 18:07 [PATCH v2 0/2] Fix request deferral for NFS/RDMA Chuck Lever
2022-04-06 18:08 ` [PATCH v2 1/2] SUNRPC: Fix NFSD's request deferral on RDMA transports Chuck Lever
2022-04-06 18:08 ` [PATCH v2 2/2] SUNRPC: Fix the svc_deferred_event trace class Chuck Lever
2022-04-06 20:34   ` Trond Myklebust [this message]
2022-04-06 20:55     ` Chuck Lever III
2022-04-06 21:17       ` Trond Myklebust
2022-04-07  0:37         ` Chuck Lever III
2022-04-07  1:27           ` 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=7976abc7a7ea7bbc445256884d0164a1b3ac5bb6.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=chuck.lever@oracle.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