Skip to content

tracing: memcpy->strncpy changes for comm strings

Tom Zanussi lkml 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2tracing: Use strncpy instead of memcpy when copying comm for hist triggerskernel/trace/trace_events_hist.c+2 -20 replies
2/2tracing: Use strncpy instead of memcpy when copying comm in trace.ckernel/trace/trace.c+2 -20 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] tracing: memcpy->strncpy changes for comm strings

From: Tom Zanussi <[email protected]>

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(-)
Signature · 1 line
2.14.1