mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Azeem Shaikh' <azeemshaikh38@gmail.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	Jeff Layton <jlayton@kernel.org>
Cc: "linux-hardening@vger.kernel.org"
	<linux-hardening@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v3] NFSD: Remove open coding of string copy
Date: Tue, 16 May 2023 09:33:58 +0000	[thread overview]
Message-ID: <d48a166d1cbc477f9cf063e91f7b3005@AcuMS.aculab.com> (raw)
In-Reply-To: <20230515024044.2677124-1-azeemshaikh38@gmail.com>

From: Azeem Shaikh
> Sent: 15 May 2023 03:41
> 
> Instead of open coding a __dynamic_array(), use the __string() and
> __assign_str() helper macros that exist for this kind of use case.

Is this actually a dynamic array, or just a char[8] ?
On 64 bit copying a short fixed-length string is far better
than any kind of dynamic sized allocation.

	David

> 
> Part of an effort to remove deprecated strlcpy() [1] completely from the
> kernel[2].
> 
> [1] https://www.kernel.org/doc/html/latest/process/deprecated.html#strlcpy
> [2] https://github.com/KSPP/linux/issues/89
> 
> Fixes: 3c92fba557c6 ("NFSD: Enhance the nfsd_cb_setup tracepoint")
> Signed-off-by: Azeem Shaikh <azeemshaikh38@gmail.com>
> ---
>  fs/nfsd/trace.h |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> 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))
>  );
> 
>  TRACE_EVENT(nfsd_cb_setup_err,
> --
> 2.40.1.606.ga4b1b128d6-goog
> 

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)


  parent reply	other threads:[~2023-05-16  9:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15  2:40 Azeem Shaikh
2023-05-15 11:21 ` Jeff Layton
2023-05-15 14:30   ` Azeem Shaikh
2023-05-16  9:33 ` David Laight [this message]
2023-05-16 14:10   ` Chuck Lever III
2023-05-16 14:36     ` David Laight

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=d48a166d1cbc477f9cf063e91f7b3005@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=azeemshaikh38@gmail.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome