Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Azeem Shaikh <azeemshaikh38@gmail.com>
Cc: Kees Cook <keescook@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Jeff Layton <jlayton@kernel.org>,
	"linux-hardening@vger.kernel.org"
	<linux-hardening@vger.kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NFSD: Replace all non-returning strlcpy with strscpy
Date: Fri, 12 May 2023 14:38:27 +0000	[thread overview]
Message-ID: <076418CA-6400-4A92-8634-60F2934F985D@oracle.com> (raw)
In-Reply-To: <CADmuW3UbHBWN0JzXMYX667hkXyWJY8_88K1sJfRnKNg7_u38=A@mail.gmail.com>



> On May 12, 2023, at 7:30 AM, Azeem Shaikh <azeemshaikh38@gmail.com> wrote:
> 
> Thanks Chuck and Kees for the review.
> 
>>> Actually netid should use the __string() and __assign_str()
>>> macros rather than open-coding a string copy, I think.
> 
> Do you mean something like this?
> 
> diff --git a/fs/nfsd/trace.h b/fs/nfsd/trace.h
> index 4183819ea082..72a906a053dc 100644
> --- a/fs/nfsd/trace.h
> +++ b/fs/nfsd/trace.h
> @@ -1365,19 +1365,19 @@ TRACE_EVENT(nfsd_cb_setup,
>                __field(u32, cl_id)
>                __field(unsigned long, authflavor)
>                __sockaddr(addr, clp->cl_cb_conn.cb_addrlen)
> -               __array(unsigned char, netid, 8)
> +               __string(netid, netid)
>        ),
>        TP_fast_assign(
>                __entry->cl_boot = clp->cl_clientid.cl_boot;
>                __entry->cl_id = clp->cl_clientid.cl_id;
> -               strlcpy(__entry->netid, netid, sizeof(__entry->netid));
> +               __assign_str(netid, netid);
>                __entry->authflavor = authflavor;
>                __assign_sockaddr(addr, &clp->cl_cb_conn.cb_addr,
>                                  clp->cl_cb_conn.cb_addrlen)
>        ),
>        TP_printk("addr=%pISpc client %08x:%08x proto=%s flavor=%s",
>                __get_sockaddr(addr), __entry->cl_boot, __entry->cl_id,
> -               __entry->netid, show_nfsd_authflavor(__entry->authflavor))
> +               __get_str(netid), show_nfsd_authflavor(__entry->authflavor))
> );

Yes. I don't remember why I chose to open-code the string
handling in here.

I agree with Kees, also: __assign_str() needs to handle
the memory accesses properly, and I had assumed it did
that already. My bad. That IMO should be handled as a
separate patch.


>>> Fixes: 3c92fba557c6 ("NFSD: Enhance the nfsd_cb_setup tracepoint")
> 
> Ack.

I agree that it's not a high priority backport. However,
I expect those who want to use trace points on KASAN-
enabled stable kernels might prefer to have the
__assign_str fix in place, along with this one.

So, I'm good with including Fixes: or leaving it off. Up
to you!

--
Chuck Lever



  reply	other threads:[~2023-05-12 14:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 22:09 [PATCH] NFSD: Replace all non-returning strlcpy with strscpy Azeem Shaikh
2023-05-11 14:47 ` Chuck Lever III
2023-05-11 16:32   ` Kees Cook
2023-05-12 14:30     ` Azeem Shaikh
2023-05-12 14:38       ` Chuck Lever III [this message]
2023-05-12 14:47         ` Azeem Shaikh
2023-05-13 23:46     ` Steven Rostedt

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=076418CA-6400-4A92-8634-60F2934F985D@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=azeemshaikh38@gmail.com \
    --cc=jlayton@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rostedt@goodmis.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