linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 0/2] tracing: memcpy->strncpy changes for comm strings
@ 2019-03-05 16:11 Tom Zanussi
  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
  0 siblings, 2 replies; 3+ messages in thread
From: Tom Zanussi @ 2019-03-05 16:11 UTC (permalink / raw)
  To: rostedt; +Cc: linux-kernel

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-03-05 16:12 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-05 16:11 [PATCH 0/2] tracing: memcpy->strncpy changes for comm strings Tom Zanussi
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).