The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: david.laight.linux@gmail.com
Cc: Kees Cook <kees@kernel.org>,
	linux-hardening@vger.kernel.org, Arnd Bergmann <arnd@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH next] drivers/iio/test: Use strscpy() to copy the test description
Date: Sun, 14 Jun 2026 19:13:55 +0100	[thread overview]
Message-ID: <20260614191355.04ca0a34@jic23-huawei> (raw)
In-Reply-To: <20260606202633.5018-37-david.laight.linux@gmail.com>

On Sat,  6 Jun 2026 21:26:31 +0100
david.laight.linux@gmail.com wrote:

> From: David Laight <david.laight.linux@gmail.com>
> 
> The buffer length is known to be KUNIT_PARAM_DESC_SIZE
> 
> Signed-off-by: David Laight <david.laight.linux@gmail.com>
Hi David,

Given all the names are set in this file, I'm taking this as a hardening
patch against future problems.

Applied to the testing branch of iio.git which will be rebased on rc1
once available.

thanks,

Jonathan

> ---
> This is one of a group of patches that remove potentially unbounded
> strcpy() calls.
> 
> They are mostly replaced by strscpy() or, when strlen() has just been
> called, with memcpy() (usually including the '\0').
> 
> Calls with copy string literals into arrays are left unchanged.
> They are safe and easily detected as such.
> 
> The changes were made by getting the compiler to detect the calls and
> then fixing the code by hand.
> 
> Note that all the changes are only compile tested.
> 
> Some Makefiles were changed to allow files to contain strcpy().
> As well as 'difficult to fix' files, this included 'show' functions
> as they really need to use sysfs_emit() or seq_printf().
> 
> All the patches are being sent individually to avoid very long cc lists.
> Apologies for the terse commit messages and likely unexpected tags.
> (There are about 100 patches in total.)
> 
>  drivers/iio/test/iio-test-rescale.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/test/iio-test-rescale.c b/drivers/iio/test/iio-test-rescale.c
> index ac6942cf1e44..bcd4a607be19 100644
> --- a/drivers/iio/test/iio-test-rescale.c
> +++ b/drivers/iio/test/iio-test-rescale.c
> @@ -575,7 +575,7 @@ static const struct rescale_tc_data offset_cases[] = {
>  
>  static void case_to_desc(const struct rescale_tc_data *t, char *desc)
>  {
> -	strcpy(desc, t->name);
> +	strscpy(desc, t->name, KUNIT_PARAM_DESC_SIZE);
>  }
>  
>  KUNIT_ARRAY_PARAM(iio_rescale_scale, scale_cases, case_to_desc);


      reply	other threads:[~2026-06-14 18:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-06 20:26 [PATCH next] drivers/iio/test: Use strscpy() to copy the test description david.laight.linux
2026-06-14 18:13 ` Jonathan Cameron [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=20260614191355.04ca0a34@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=arnd@kernel.org \
    --cc=david.laight.linux@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@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