From: Tom Zanussi <zanussi@kernel.org>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] tracing: memcpy->strncpy changes for comm strings
Date: Tue, 5 Mar 2019 10:11:58 -0600 [thread overview]
Message-ID: <cover.1551802084.git.tom.zanussi@linux.intel.com> (raw)
From: Tom Zanussi <tom.zanussi@linux.intel.com>
Hi Steve,
Here are a couple patches as discussed, replacing memcpy with strncpy
for comm strings in trace.c and trace_events_hist.c.
Thanks,
Tom
The following changes since commit 9f0bbf3115ca9f91f43b7c74e9ac7d79f47fc6c2:
tracing: Use strncpy instead of memcpy for string keys in hist triggers (2019-03-05 08:47:46 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/zanussi/linux-trace.git ftrace/comm-strncpy
Tom Zanussi (2):
tracing: Use strncpy instead of memcpy when copying comm for hist
triggers
tracing: Use strncpy instead of memcpy when copying comm in trace.c
kernel/trace/trace.c | 4 ++--
kernel/trace/trace_events_hist.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.14.1
next reply other threads:[~2019-03-05 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 16:11 Tom Zanussi [this message]
2019-03-05 16:11 ` [PATCH 1/2] tracing: Use strncpy instead of memcpy when copying comm for hist triggers Tom Zanussi
2019-03-05 16:12 ` [PATCH 2/2] tracing: Use strncpy instead of memcpy when copying comm in trace.c Tom Zanussi
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=cover.1551802084.git.tom.zanussi@linux.intel.com \
--to=zanussi@kernel.org \
--cc=linux-kernel@vger.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