linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tom Zanussi <zanussi@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
	kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.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 10:49:51 -0500	[thread overview]
Message-ID: <20220310104951.60d0adb6@gandalf.local.home> (raw)
In-Reply-To: <93bb0a79331882df8ce2bf704b3d4ac28c8cbc3d.camel@kernel.org>

On Thu, 10 Mar 2022 09:12:39 -0600
Tom Zanussi <zanussi@kernel.org> wrote:

> 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...

I don't rebase my linux-next branch unless there's a really go reason to do
so. But I also have this patch going through my testing:

  https://lore.kernel.org/all/20220308110736.479e3cc9@gandalf.local.home/

Which I believe fixes the issue.

But we can use this patch too, but I do get nervous about plain strcat().

-- Steve


  reply	other threads:[~2022-03-10 15:49 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
2022-03-10 15:49   ` Steven Rostedt [this message]
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=20220310104951.60d0adb6@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=zanussi@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