All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Maxim Krasnyansky <maxk@qti.qualcomm.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: networking: Replace strncpy() with strscpy()
Date: Wed, 2 Jun 2021 21:40:28 -0700	[thread overview]
Message-ID: <YLhdPEFO2zdzWef+@google.com> (raw)
In-Reply-To: <20210602202914.4079123-1-keescook@chromium.org>

On Wed, Jun 02, 2021 at 01:29:14PM -0700, Kees Cook wrote:
> Replace example code's use of strncpy() with strscpy() functions. Using
> strncpy() is considered deprecated:
> https://www.kernel.org/doc/html/latest/process/deprecated.html#strncpy-on-nul-terminated-strings
> 
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
>  Documentation/input/joydev/joystick-api.rst | 2 +-

FWIW:

Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

>  Documentation/networking/packet_mmap.rst    | 2 +-
>  Documentation/networking/tuntap.rst         | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/input/joydev/joystick-api.rst b/Documentation/input/joydev/joystick-api.rst
> index af5934c10c1c..5db6dc6fe1c5 100644
> --- a/Documentation/input/joydev/joystick-api.rst
> +++ b/Documentation/input/joydev/joystick-api.rst
> @@ -263,7 +263,7 @@ possible overrun should the name be too long::
>  
>  	char name[128];
>  	if (ioctl(fd, JSIOCGNAME(sizeof(name)), name) < 0)
> -		strncpy(name, "Unknown", sizeof(name));
> +		strscpy(name, "Unknown", sizeof(name));
>  	printf("Name: %s\n", name);
>  
>  
> diff --git a/Documentation/networking/packet_mmap.rst b/Documentation/networking/packet_mmap.rst
> index 500ef60b1b82..c5da1a5d93de 100644
> --- a/Documentation/networking/packet_mmap.rst
> +++ b/Documentation/networking/packet_mmap.rst
> @@ -153,7 +153,7 @@ As capture, each frame contains two parts::
>      struct ifreq s_ifr;
>      ...
>  
> -    strncpy (s_ifr.ifr_name, "eth0", sizeof(s_ifr.ifr_name));
> +    strscpy_pad (s_ifr.ifr_name, "eth0", sizeof(s_ifr.ifr_name));
>  
>      /* get interface index of eth0 */
>      ioctl(this->socket, SIOCGIFINDEX, &s_ifr);
> diff --git a/Documentation/networking/tuntap.rst b/Documentation/networking/tuntap.rst
> index a59d1dd6fdcc..4d7087f727be 100644
> --- a/Documentation/networking/tuntap.rst
> +++ b/Documentation/networking/tuntap.rst
> @@ -107,7 +107,7 @@ Note that the character pointer becomes overwritten with the real device name
>         */
>        ifr.ifr_flags = IFF_TUN;
>        if( *dev )
> -	 strncpy(ifr.ifr_name, dev, IFNAMSIZ);
> +	 strscpy_pad(ifr.ifr_name, dev, IFNAMSIZ);
>  
>        if( (err = ioctl(fd, TUNSETIFF, (void *) &ifr)) < 0 ){
>  	 close(fd);
> -- 
> 2.25.1
> 

Thanks.

-- 
Dmitry

  reply	other threads:[~2021-06-03  4:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 20:29 [PATCH] docs: networking: Replace strncpy() with strscpy() Kees Cook
2021-06-03  4:40 ` Dmitry Torokhov [this message]
2021-06-04 17:22 ` Jonathan Corbet

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=YLhdPEFO2zdzWef+@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=corbet@lwn.net \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qti.qualcomm.com \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.