| 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
| ||
|
Message-ID: <YNIobHgfVbiiNscn@kernel.org>
Date: Tue, 22 Jun 2021 15:14:04 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Ian Rogers <irogers@...gle.com>
Cc: Jiri Olsa <jolsa@...hat.com>, lkml <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Namhyung Kim <namhyung@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Michael Petlan <mpetlan@...hat.com>, rickyman7@...il.com
Subject: Re: [RFC 00/10] perf: Add build id parsing fault detection/fix
Em Tue, Jun 22, 2021 at 10:47:54AM -0700, Ian Rogers escreveu:
> On Tue, Jun 22, 2021 at 10:39 AM Arnaldo Carvalho de Melo
> <acme@...nel.org> wrote:
> >
> > Em Tue, Jun 22, 2021 at 05:39:08PM +0200, Jiri Olsa escreveu:
> > > hi,
> > > this *RFC* patchset adds support to detect faults during
> > > mmap2's build id parsing and a way to fix such maps in
> > > generated perf.data.
> > >
> > > It adds support to record build id faults count for session
> > > and store it in perf.data and perf inject support to find
> > > these maps and reads build ids for them in user space.
> >
> > > It's probably best explained by the workflow:
> > >
> > > Record data with --buildid-mmap option:
> > >
> > > # perf record --buildid-mmap ...
> > > ...
> > > [ perf record: Woken up 1 times to write data ]
> > > [ perf record: Failed to parse 4 build ids]
> > > [ perf record: Captured and wrote 0.008 MB perf.data ]
> > >
> > > Check if there's any build id fault reported:
> > >
> > > # perf report --header-only
> > > ...
> > > # build id mmap stats: FAULTS 4, LOST 0, NOT FIXED
> > >
> > > There is, check the stats:
> > >
> > > # perf report --stat
> > >
> > > Aggregated stats:
> > > TOTAL events: 104
> > > ....
> > > BUILD_ID fails: 4 (14.3%)
> > >
> > > Yep, let's fix it:
> > >
> > > # perf inject --buildid-mmap2 -i perf.data -o perf-fixed.data
> >
> > Can we make it possible to automate this with --fixup-buildids or a
> > perfconfig 'record' knob?
> >
> > This would entail requesting that build-ids that _fail_ be sent to the
> > side-band thread we have in 'perf record', this way we wouldn't have to
> > traverse the whole perf.data file, be it with 'perf-record' at the end
> > of a session with faulty build ids, or in a similar fashion using 'perf
> > inject' as you suggest.
> >
> > I even think that we can have all these modes and let the user to decide
> > how important is this for them and how convenient they want the whole
> > process to be.
>
> Firstly thanks for the patches! To Arnaldo's sideband idea, I wonder
> if we have a thread doing sideband buildid generation whether the same
> thread or threads could also be doing the synthesis job. Perhaps such
> work could be postponed until when the session closes, like with tail
I didn't suggest synthesizing the failed build-ids in the sideband
thread, just receiving the MMAP2 records for the build-ids that
faulted.
It may be interesting to do it right away, to avoid building up a
potentially large number of entries to do at the end, but if this is
something uncommon, with just a few entries, then leaving it for after
the workload finishes may be a good idea.
Or perhaps this needs to be a knob, since for long running sessions such
as with 'perf daemon' the "workload" may never end, so we better flush
these things as the files where we'll get it from may go away.
> synthesis. It's a particular shame with tail synthesis that we
> synthesize mmap events for processes with no samples.
Sure, but it is also very costly to process a potentially large
perf.data file for looking at what MMAPs have samples. That is the
raison d'être for PERF_RECORD_MMAP2 to carry build-ids :-)
I.e. there are pros and cons for tail synthesis, for looking at all
samples to generate only build-ids for MMAPs with hits, for synthesizing
it in the sideband thread immediately, for leaving this generation to
be done at the end by traversing the list of MMAP records without
build-ids, etc.
- Arnaldo
> Thanks,
> Ian
>
> > - Arnaldo
> >
> > > And verify:
> > >
> > > # perf report -i perf-fixed.data --stats
> > >
> > > Aggregated stats:
> > > TOTAL events: 104
> > > ....
> > >
> > > Good, let's see how many we fixed:
> > >
> > > # perf report --header-only -i perf-fixed.data
> > > ...
> > > # build id mmap stats: FAULTS 4, LOST 0, FIXED(4)
> > >
> > >
> > > I don't have a good way to test it, just by artificially
> > > adding the faults in kernel code, but Ian and Namhyung
> > > might have setup that could generate that.. would be great
> > > to have a perf test for this.
> > >
> > > Also available in here:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
> > > perf/buildid_stats
> > >
> > > thoughts?
> > >
> > > thanks,
> > > jirka
> > >
> > >
> > > ---
> > > Jiri Olsa (10):
> > > perf: Track build id faults for mmap2 event
> > > perf: Move build_id_parse to check only regular files
> > > perf: Add new read_format bit to read build id faults
> > > perf: Add new read_format bit to read lost events
> > > tools: Sync perf_event.h uapi
> > > libperf: Do not allow PERF_FORMAT_GROUP in perf_evsel__read
> > > perf record: Add support to read build id fails
> > > perf record: Add new HEADER_BUILD_ID_MMAP feature
> > > perf report: Display build id fails stats
> > > perf inject: Add --buildid-mmap2 option to fix failed build ids
> > >
> > > include/linux/perf_event.h | 2 ++
> > > include/uapi/linux/perf_event.h | 20 +++++++++++++-------
> > > kernel/events/core.c | 49 +++++++++++++++++++++++++++++++++++++++++++------
> > > kernel/events/ring_buffer.c | 3 +++
> > > tools/include/uapi/linux/perf_event.h | 20 +++++++++++++-------
> > > tools/lib/perf/evsel.c | 10 ++++++++++
> > > tools/lib/perf/include/perf/evsel.h | 11 ++++++++++-
> > > tools/perf/Documentation/perf-inject.txt | 3 +++
> > > tools/perf/Documentation/perf.data-file-format.txt | 19 +++++++++++++++++++
> > > tools/perf/builtin-inject.c | 45 +++++++++++++++++++++++++++++++++++++++++++--
> > > tools/perf/builtin-record.c | 97 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > > tools/perf/builtin-report.c | 35 +++++++++++++++++++++++++++++++++++
> > > tools/perf/util/env.h | 6 ++++++
> > > tools/perf/util/evsel.c | 12 ++++++++++++
> > > tools/perf/util/header.c | 80 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > > tools/perf/util/header.h | 1 +
> > > tools/perf/util/map.h | 15 +++++++++++++++
> > > tools/perf/util/perf_event_attr_fprintf.c | 3 ++-
> > > 18 files changed, 407 insertions(+), 24 deletions(-)
> > >
> >
> > --
> >
> > - Arnaldo
--
- Arnaldo
Powered by blists - more mailing lists