From: Tom Zanussi <zanussi@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: Re: [linux-next:master 4605/11713] kernel/trace/trace_events_synth.c:65:9: warning: 'strncpy' specified bound depends on the length of the source argument
Date: Thu, 10 Mar 2022 09:12:39 -0600 [thread overview]
Message-ID: <93bb0a79331882df8ce2bf704b3d4ac28c8cbc3d.camel@kernel.org> (raw)
In-Reply-To: <202203092349.i2I1pdlw-lkp@intel.com>
On Wed, 2022-03-09 at 23:48 +0800, kernel test robot wrote:
> Hi Tom,
>
> FYI, the error/warning still remains.
>
>
Thanks, the patch below fixes it. I'll submit to lkml, but not sure
whether to submit the fix or resubmit the original patch...
Tom
[PATCH] tracing: Fix strncpy warning in trace_events_synth.c
0-day reported the strncpy error below:
../kernel/trace/trace_events_synth.c: In function 'last_cmd_set':
../kernel/trace/trace_events_synth.c:65:9: warning: 'strncpy' specified bound depends on the length o\
f the source argument [-Wstringop-truncation]
65 | strncpy(last_cmd, str, strlen(str) + 1);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../kernel/trace/trace_events_synth.c:65:32: note: length computed here
65 | strncpy(last_cmd, str, strlen(str) + 1);
| ^~~~~~~~~~~
There's no reason to use strncpy here, since the buffer being copied
to was just allocated as strlen(str) + 1, and therefore the strcpy()
of str will exactly fit, including the null terminator.
Fixes: 27c888da9867 ("tracing: Remove size restriction on synthetic event cmd error logging")
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Tom Zanussi <zanussi@kernel.org>
---
kernel/trace/trace_events_synth.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/trace_events_synth.c b/kernel/trace/trace_events_synth.c
index fdd79e07e2fc..a133396ee29d 100644
--- a/kernel/trace/trace_events_synth.c
+++ b/kernel/trace/trace_events_synth.c
@@ -62,7 +62,7 @@ static void last_cmd_set(const char *str)
if (!last_cmd)
return;
- strncpy(last_cmd, str, strlen(str) + 1);
+ strcpy(last_cmd, str);
}
static void synth_err(u8 err_type, u16 err_pos)
--
2.17.1
next prev parent reply other threads:[~2022-03-10 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 15:48 kernel test robot
2022-03-10 15:12 ` Tom Zanussi [this message]
2022-03-10 15:49 ` Steven Rostedt
2022-03-10 16:08 ` Tom Zanussi
2022-03-10 16:26 ` Steven Rostedt
2022-03-10 16:45 ` Tom Zanussi
2022-03-10 17:07 ` 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=93bb0a79331882df8ce2bf704b3d4ac28c8cbc3d.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--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