From: Tom Zanussi <zanussi@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mhiramat@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] tracing: Misc bugfixes
Date: Fri, 28 Jan 2022 15:50:45 -0600 [thread overview]
Message-ID: <52c7f9e7effb6bd09d35b95bdca056a3e0907667.camel@kernel.org> (raw)
In-Reply-To: <20220128164219.1a5189cd@gandalf.local.home>
On Fri, 2022-01-28 at 16:42 -0500, Steven Rostedt wrote:
> On Fri, 28 Jan 2022 14:08:25 -0600
> Tom Zanussi <zanussi@kernel.org> wrote:
>
> > There were 2 patches in v1 that were flagged by the 0day robot for
> > strncpy off-by-1 warnings:
> >
> > tracing: Remove size restriction on hist trigger cmd error
> > logging
> > tracing: Remove size restriction on synthetic event cmd error
> > logging
> >
> > warning: 'strncpy' output truncated before terminating nul
> > copying
> > as many bytes from a string as its length [-Wstringop-truncation]
> >
> > This v2 patchset consists of just those two patches with the fix
> > for
> > those warnings.
>
>
> So this just replaces the last two patches you sent previously?
>
Yes.
> Probably would have been better to send all three (since the other 4
> already made it into mainline).
>
OK, yeah, thought about doing that but guessed wrong, as usual ;-)
> But if "tracing: Remove size restriction on tracing_log_err cmd
> strings" is
> OK:
>
>
Yeah, that one is ok as-is without changes.
Tom
>
https://lkml.kernel.org/r/ca965f23256b350ebd94b3dc1a319f28e8267f5f.1643319703.git.zanussi@kernel.org
>
> then I'll just replace the other two.
>
> -- Steve
prev parent reply other threads:[~2022-01-28 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 20:08 Tom Zanussi
2022-01-28 20:08 ` [PATCH v2 1/2] tracing: Remove size restriction on hist trigger cmd error logging Tom Zanussi
2022-01-28 20:08 ` [PATCH v2 2/2] tracing: Remove size restriction on synthetic event " Tom Zanussi
2022-01-28 21:42 ` [PATCH v2 0/2] tracing: Misc bugfixes Steven Rostedt
2022-01-28 21:50 ` Tom Zanussi [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=52c7f9e7effb6bd09d35b95bdca056a3e0907667.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--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
Powered by JetHome