From: Alan Maguire <alan.maguire@oracle.com>
To: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org
Cc: kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
quentin@isovalent.com, toke@redhat.com, bpf@vger.kernel.org,
netdev@vger.kernel.org, Alan Maguire <alan.maguire@oracle.com>
Subject: [PATCH bpf-next 0/3] tools: ksnoop: tracing kernel function entry/return with argument/return value display
Date: Tue, 3 Aug 2021 22:23:13 +0100 [thread overview]
Message-ID: <1628025796-29533-1-git-send-email-alan.maguire@oracle.com> (raw)
Recent functionality added to libbpf [1] enables typed display of kernel
data structures; here that functionality is exploited to provide a
simple example of how a tracer can support deep argument/return value
inspection. The intent is to provide a demonstration of these features
to help facilitate tracer adoption, while also providing a tool which
can be useful for kernel debugging.
Changes since RFC [2]:
- In the RFC version, kernel data structures were string-ified in
BPF program context vi bpf_snprintf_btf(); Alexei pointed out that
it would be better to dump memory to userspace and let the
interpretation happen there. btf_dump__dump_type_data() in libbpf
now supports this (Alexei, patch 1)
- Added the "stack mode" specification where we trace a specific set
of functions being called in order (though not necessarily directly).
This mode of tracing is useful when debugging issues with a specific
stack signature.
[1] https://lore.kernel.org/bpf/1626362126-27775-1-git-send-email-alan.maguire@oracle.com/
[2] https://lore.kernel.org/bpf/1609773991-10509-1-git-send-email-alan.maguire@oracle.com/
Alan Maguire (3):
tools: ksnoop: kernel argument/return value tracing/display using BTF
tools: ksnoop: document ksnoop tracing of entry/return with value
display
tools: ksnoop: add .gitignore
tools/bpf/Makefile | 20 +-
tools/bpf/ksnoop/.gitignore | 1 +
tools/bpf/ksnoop/Documentation/Makefile | 58 ++
tools/bpf/ksnoop/Documentation/ksnoop.rst | 173 ++++++
tools/bpf/ksnoop/Makefile | 107 ++++
tools/bpf/ksnoop/ksnoop.bpf.c | 391 +++++++++++++
tools/bpf/ksnoop/ksnoop.c | 890 ++++++++++++++++++++++++++++++
tools/bpf/ksnoop/ksnoop.h | 103 ++++
8 files changed, 1738 insertions(+), 5 deletions(-)
create mode 100644 tools/bpf/ksnoop/.gitignore
create mode 100644 tools/bpf/ksnoop/Documentation/Makefile
create mode 100644 tools/bpf/ksnoop/Documentation/ksnoop.rst
create mode 100644 tools/bpf/ksnoop/Makefile
create mode 100644 tools/bpf/ksnoop/ksnoop.bpf.c
create mode 100644 tools/bpf/ksnoop/ksnoop.c
create mode 100644 tools/bpf/ksnoop/ksnoop.h
--
1.8.3.1
next reply other threads:[~2021-08-03 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 21:23 Alan Maguire [this message]
2021-08-03 21:23 ` [PATCH bpf-next 1/3] tools: ksnoop: kernel argument/return value tracing/display using BTF Alan Maguire
2021-08-03 21:23 ` [PATCH bpf-next 2/3] tools: ksnoop: document ksnoop tracing of entry/return with value display Alan Maguire
2021-08-03 21:23 ` [PATCH bpf-next 3/3] tools: ksnoop: add .gitignore Alan Maguire
2021-08-04 21:05 ` [PATCH bpf-next 0/3] tools: ksnoop: tracing kernel function entry/return with argument/return value display Daniel Borkmann
2021-08-05 11:14 ` Alan Maguire
2021-08-06 14:56 ` Daniel Borkmann
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=1628025796-29533-1-git-send-email-alan.maguire@oracle.com \
--to=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=songliubraving@fb.com \
--cc=toke@redhat.com \
--cc=yhs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.