diff options
| author | He Zhe <zhe.he@windriver.com> | 2020-08-14 03:10:51 +0000 |
|---|---|---|
| committer | Khem Raj <raj.khem@gmail.com> | 2020-08-14 06:56:50 -0700 |
| commit | 2353b178067522545cc0e892789d5b87c1213fdd (patch) | |
| tree | e90d3a468c67a47ae4125886c02347594815959d /CODE_OF_CONDUCT.md | |
| parent | ccb0a3a786e5f59ec681a013be94ddd0d9e97ec9 (diff) | |
| download | meta-clang-2353b178067522545cc0e892789d5b87c1213fdd.tar.gz | |
bcc: biosnoop: Fix failing to attach to trace_req_completion
/usr/share/bcc/tools/biosnoop
cannot attach kprobe, probe entry may not exist
Traceback (most recent call last):
File "/usr/share/bcc/tools/biosnoop", line 162, in <module>
b.attach_kprobe(event="blk_account_io_completion",
File "/usr/lib64/python3.8/site-packages/bcc/_init_.py", line 660, in attach_kprobe
raise Exception("Failed to attach BPF program %s to kprobe %s" %
Exception: Failed to attach BPF program b'trace_req_completion' to kprobe b'blk_account_io_completion'
The kernel function "blk_account_io_completion" is not available anymore
as attach point of Kprobe as of kernel version 5.8.0. Therefore, after
discussions, we decided to use function "blk_account_io_done" instead in
every kprobe attachment to "blk_account_io_completion".
Signed-off-by: He Zhe <zhe.he@windriver.com>
Diffstat (limited to 'CODE_OF_CONDUCT.md')
0 files changed, 0 insertions, 0 deletions