Commit 80a2c7be authored by David Carrillo-Cisneros's avatar David Carrillo-Cisneros Committed by Greg Kroah-Hartman

perf inject: Copy events when reordering events in pipe mode


[ Upstream commit 1e0d4f02 ]

__perf_session__process_pipe_events reuses the same memory buffer to
process all events in the pipe.

When reordering is needed (e.g. -b option), events are not immediately
flushed, but kept around until reordering is possible, causing
memory corruption.

The problem is usually observed by a "Unknown sample error" output. It
can easily be reproduced by:

  perf record -o - noploop | perf inject -b > output

Committer testing:

Before:

  $ perf record -o - stress -t 2 -c 2 | perf inject -b > /dev/null
  stress: info: [8297] dispatching hogs: 2 cpu, 0 io, 0 vm, 0 hdd
  stress: info: [8297] successful run completed in 2s
  [ perf record: Woken up 3 times to write data ]
  [ perf record: Captured and wrote 0.000 MB - ]
  Warning:
  Found 1 unknown events!

  Is this an older tool processing a perf.data file generated by a more recent tool?

  If that is not the case, consider reporting to linux-kernel@vger.kernel.org.

  $

After:

  $ perf record -o - stress -t 2 -c 2 | perf inject -b > /dev/null
  stress: info: [9027] dispatching hogs: 2 cpu, 0 io, 0 vm, 0 hdd
  stress: info: [9027] successful run completed in 2s
  [ perf record: Woken up 3 times to write data ]
  [ perf record: Captured and wrote 0.000 MB - ]
  no symbols found in /usr/bin/stress, maybe install a debug package?
  no symbols found in /usr/bin/stress, maybe install a debug package?
  $
Signed-off-by: default avatarDavid Carrillo-Cisneros <davidcc@google.com>
Tested-by: default avatarArnaldo Carvalho de Melo <acme@redhat.com>
Acked-by: default avatarJiri Olsa <jolsa@kernel.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: He Kuang <hekuang@huawei.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Paul Turner <pjt@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Simon Que <sque@chromium.org>
Cc: Stephane Eranian <eranian@google.com>
Cc: Wang Nan <wangnan0@huawei.com>
Link: http://lkml.kernel.org/r/20170410201432.24807-3-davidcc@google.comSigned-off-by: default avatarArnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: default avatarSasha Levin <alexander.levin@microsoft.com>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent f71cd02d
...@@ -79,7 +79,7 @@ static union perf_event *dup_event(struct ordered_events *oe, ...@@ -79,7 +79,7 @@ static union perf_event *dup_event(struct ordered_events *oe,
static void free_dup_event(struct ordered_events *oe, union perf_event *event) static void free_dup_event(struct ordered_events *oe, union perf_event *event)
{ {
if (oe->copy_on_queue) { if (event && oe->copy_on_queue) {
oe->cur_alloc_size -= event->header.size; oe->cur_alloc_size -= event->header.size;
free(event); free(event);
} }
...@@ -150,6 +150,7 @@ void ordered_events__delete(struct ordered_events *oe, struct ordered_event *eve ...@@ -150,6 +150,7 @@ void ordered_events__delete(struct ordered_events *oe, struct ordered_event *eve
list_move(&event->list, &oe->cache); list_move(&event->list, &oe->cache);
oe->nr_events--; oe->nr_events--;
free_dup_event(oe, event->event); free_dup_event(oe, event->event);
event->event = NULL;
} }
int ordered_events__queue(struct ordered_events *oe, union perf_event *event, int ordered_events__queue(struct ordered_events *oe, union perf_event *event,
......
...@@ -1437,6 +1437,7 @@ static int __perf_session__process_pipe_events(struct perf_session *session) ...@@ -1437,6 +1437,7 @@ static int __perf_session__process_pipe_events(struct perf_session *session)
buf = malloc(cur_size); buf = malloc(cur_size);
if (!buf) if (!buf)
return -errno; return -errno;
ordered_events__set_copy_on_queue(oe, true);
more: more:
event = buf; event = buf;
err = readn(fd, event, sizeof(struct perf_event_header)); err = readn(fd, event, sizeof(struct perf_event_header));
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment