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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 11 Jan 2021 18:49:58 -0800
From:   Alexei Starovoitov <>
To:     Jiri Olsa <>
Cc:     Arnaldo Carvalho de Melo <>,
        lkml <>,
        Peter Zijlstra <>,
        Ingo Molnar <>,
        Mark Rutland <>,
        Namhyung Kim <>,
        Alexander Shishkin <>,
        Michael Petlan <>,
        Song Liu <>,
        Ian Rogers <>,
        Stephane Eranian <>,
        Alexei Budankov <>,
        Andi Kleen <>,
        Adrian Hunter <>
Subject: Re: [PATCHv6 0/4] perf: Add mmap2 build id support

On Mon, Jan 11, 2021 at 10:38:19PM +0100, Jiri Olsa wrote:
> hi,
> adding the support to have buildid stored in mmap2 event,
> so we can bypass the final perf record hunt on build ids.
> This patchset allows perf to record build ID in mmap2 event,
> and adds perf tooling to store/download binaries to .debug
> cache based on these build IDs.
> Note that the build id retrieval code is stolen from bpf
> code, where it's been used (together with file offsets)
> to replace IPs in user space stack traces. It's now added
> under lib directory.
> v6 changes:
>   - last 4 patches rebased Arnaldo's perf/core

There were no issues with v5 as far as I can remember.
This is just a resubmit to get it landed ?
Last time we couldn't quite figure out which tree to go through.
I think the recommend path was to go via bpf-next.
Is it still the case?

Powered by blists - more mailing lists