From: Song Liu <songliubraving@fb.com>
To: <netdev@vger.kernel.org>, <ast@kernel.org>,
<peterz@infradead.org>, <daniel@iogearbox.net>
Cc: <kernel-team@fb.com>, <hannes@cmpxchg.org>, <qinteng@fb.com>,
Song Liu <songliubraving@fb.com>
Subject: [PATCH bpf-next v4 0/2] bpf stackmap with build_id+offset
Date: Mon, 12 Mar 2018 13:39:55 -0700 [thread overview]
Message-ID: <20180312203957.2025833-1-songliubraving@fb.com> (raw)
This is v4 of this work. Changes since v3:
1. Add fallback when build_id lookup failed. In this case, status is set
to BPF_STACK_BUILD_ID_IP, and ip of this entry is saved.
2. Handle cases where vma is only part of the file (vma->vm_pgoff != 0).
Thanks to Teng for helping me identify this issue!
3. Address feedbacks for previous versions.
Song Liu (2):
bpf: extend stackmap to save binary_build_id+offset instead of address
bpf: add selftest for stackmap with BPF_F_STACK_BUILD_ID
include/uapi/linux/bpf.h | 22 ++
kernel/bpf/stackmap.c | 251 +++++++++++++++++++--
tools/include/uapi/linux/bpf.h | 22 ++
tools/testing/selftests/bpf/Makefile | 12 +-
tools/testing/selftests/bpf/test_progs.c | 164 +++++++++++++-
.../selftests/bpf/test_stacktrace_build_id.c | 60 +++++
tools/testing/selftests/bpf/urandom_read.c | 22 ++
7 files changed, 529 insertions(+), 24 deletions(-)
create mode 100644 tools/testing/selftests/bpf/test_stacktrace_build_id.c
create mode 100644 tools/testing/selftests/bpf/urandom_read.c
--
2.9.5
next reply other threads:[~2018-03-12 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 20:39 Song Liu [this message]
2018-03-12 20:39 ` [PATCH bpf-next v4 1/2] bpf: extend stackmap to save binary_build_id+offset instead of address Song Liu
2018-03-12 21:00 ` Alexei Starovoitov
2018-03-12 21:12 ` Song Liu
2018-03-12 21:31 ` Alexei Starovoitov
2018-03-12 22:47 ` Song Liu
2018-03-13 21:31 ` Song Liu
2018-03-12 22:01 ` Peter Zijlstra
2018-04-24 0:06 ` Yonghong Song
2018-03-13 9:53 ` [PATCH] bpf: fix semicolon.cocci warnings kbuild test robot
2018-03-13 9:53 ` [PATCH bpf-next v4 1/2] bpf: extend stackmap to save binary_build_id+offset instead of address kbuild test robot
2018-03-12 20:39 ` [PATCH bpf-next v4 2/2] bpf: add selftest for stackmap with BPF_F_STACK_BUILD_ID Song Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180312203957.2025833-1-songliubraving@fb.com \
--to=songliubraving@fb.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=qinteng@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox