diff options
author | Daniel Borkmann <daniel@iogearbox.net> | 2019-05-24 23:26:49 +0200 |
---|---|---|
committer | Daniel Borkmann <daniel@iogearbox.net> | 2019-05-24 23:26:50 +0200 |
commit | a08acd118d5ca7f6e745ef81cfc6cbadacb56462 (patch) | |
tree | be871dcf6d0496ed0093293e7cebb41a6b95ad0c /COPYING | |
parent | 5420f3207759cd618a7b8a04a4eb5fc1c12b35cb (diff) | |
parent | 16f0efc3b46352018c297bbdb2c405e7d8a63095 (diff) | |
download | linux-stable-a08acd118d5ca7f6e745ef81cfc6cbadacb56462.tar.gz linux-stable-a08acd118d5ca7f6e745ef81cfc6cbadacb56462.tar.bz2 linux-stable-a08acd118d5ca7f6e745ef81cfc6cbadacb56462.zip |
Merge branch 'bpf-send-sig'
Yonghong Song says:
====================
This patch tries to solve the following specific use case.
Currently, bpf program can already collect stack traces
through kernel function get_perf_callchain()
when certain events happens (e.g., cache miss counter or
cpu clock counter overflows). But such stack traces are
not enough for jitted programs, e.g., hhvm (jited php).
To get real stack trace, jit engine internal data structures
need to be traversed in order to get the real user functions.
bpf program itself may not be the best place to traverse
the jit engine as the traversing logic could be complex and
it is not a stable interface either.
Instead, hhvm implements a signal handler,
e.g. for SIGALARM, and a set of program locations which
it can dump stack traces. When it receives a signal, it will
dump the stack in next such program location.
This patch implements bpf_send_signal() helper to send
a signal to hhvm in real time, resulting in intended stack traces.
Patch #1 implemented the bpf_send_helper() in the kernel.
Patch #2 synced uapi header bpf.h to tools directory.
Patch #3 added a self test which covers tracepoint
and perf_event bpf programs.
Changelogs:
v4 => v5:
. pass the "current" task struct to irq_work as well
since the current task struct may change between
nmi and subsequent irq_work_interrupt.
Discovered by Daniel.
v3 => v4:
. fix one typo and declare "const char *id_path = ..."
to avoid directly use the long string in the func body
in Patch #3.
v2 => v3:
. change the standalone test to be part of prog_tests.
RFC v1 => v2:
. previous version allows to send signal to an arbitrary
pid. This version just sends the signal to current
task to avoid unstable pid and potential races between
sending signals and task state changes for the pid.
====================
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions