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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <cover.1551802084.git.tom.zanussi@linux.intel.com>
Date:   Tue,  5 Mar 2019 10:11:58 -0600
From:   Tom Zanussi <zanussi@...nel.org>
To:     rostedt@...dmis.org
Cc:     linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] tracing: memcpy->strncpy changes for comm strings

From: Tom Zanussi <tom.zanussi@...ux.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