Re: [PATCH v13 00/20] tracing: fprobe: function_graph: Multi-function graph and fprobe on fgraph

Andrii Nakryiko
2024-08-19T21:12:13Z

On Sun, Aug 18, 2024 at 5:58 PM Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> Hi,
>
> Where can I get the test programs? I would like to check what the programs
> actually expected.
>

Hi Masami,

This is part of BPF selftests (so it's under
tools/testing/selftests/bpf). Specifically, this test is defined in

- progs/kprobe_multi.c for BPF parts
- prog_tests/kprobe_multi_testmod_test.c for user-space parts.

It seems to be failing on arm64 (but not on x86-64, so something
architecture-specific).

> On Sun, 18 Aug 2024 13:51:30 +0000 (UTC)
> bot+bpf-ci@kernel.org wrote:
>
> > Dear patch submitter,
> >
> > CI has tested the following submission:
> > Status: FAILURE
> > Name: [v13,00/20] tracing: fprobe: function_graph: Multi-function graph and fprobe on fgraph
> > Patchwork: https://patchwork.kernel.org/project/netdevbpf/list/?series=880630&state=*
> > Matrix: https://github.com/kernel-patches/bpf/actions/runs/10440799833
> >
> > Failed jobs:
> > test_progs-aarch64-gcc: https://github.com/kernel-patches/bpf/actions/runs/10440799833/job/28911439106
> > test_progs_no_alu32-aarch64-gcc: https://github.com/kernel-patches/bpf/actions/runs/10440799833/job/28911439234
> > test_progs-s390x-gcc: https://github.com/kernel-patches/bpf/actions/runs/10440799833/job/28911405063
> > test_progs_no_alu32-s390x-gcc: https://github.com/kernel-patches/bpf/actions/runs/10440799833/job/28911404959
> > veristat-x86_64-gcc: https://github.com/kernel-patches/bpf/actions/runs/10440799833/job/28911401263
> >
> > First test_progs failure (test_progs-aarch64-gcc):
> > #126 kprobe_multi_testmod_test
> > serial_test_kprobe_multi_testmod_test:PASS:load_kallsyms_local 0 nsec
> > #126/1 kprobe_multi_testmod_test/testmod_attach_api_syms
> > test_testmod_attach_api:PASS:fentry_raw_skel_load 0 nsec
> > trigger_module_test_read:PASS:testmod_file_open 0 nsec
> > test_testmod_attach_api:PASS:trigger_read 0 nsec
> > kprobe_multi_testmod_check:FAIL:kprobe_test1_result unexpected kprobe_test1_result: actual 0 != expected 1
> > kprobe_multi_testmod_check:FAIL:kprobe_test2_result unexpected kprobe_test2_result: actual 0 != expected 1
> > kprobe_multi_testmod_check:FAIL:kprobe_test3_result unexpected kprobe_test3_result: actual 0 != expected 1
> > kprobe_multi_testmod_check:FAIL:kretprobe_test1_result unexpected kretprobe_test1_result: actual 0 != expected 1
> > kprobe_multi_testmod_check:FAIL:kretprobe_test2_result unexpected kretprobe_test2_result: actual 0 != expected 1
> > kprobe_multi_testmod_check:FAIL:kretprobe_test3_result unexpected kretprobe_test3_result: actual 0 != expected 1
> > #126/2 kprobe_multi_testmod_test/testmod_attach_api_addrs
> > test_testmod_attach_api_addrs:PASS:ksym_get_addr_local 0 nsec
> > test_testmod_attach_api_addrs:PASS:ksym_get_addr_local 0 nsec
> > test_testmod_attach_api_addrs:PASS:ksym_get_addr_local 0 nsec
> > test_testmod_attach_api:PASS:fentry_raw_skel_load 0 nsec
> > trigger_module_test_read:PASS:testmod_file_open 0 nsec
> > test_testmod_attach_api:PASS:trigger_read 0 nsec
> > kprobe_multi_testmod_check:FAIL:kprobe_test1_result unexpected kprobe_test1_result: actual 0 != expected 1
> > kprobe_multi_testmod_check:FAIL:kprobe_test2_result unexpected kprobe_test2_result: actual 0 != expected 1
> > kprobe_multi_testmod_check:FAIL:kprobe_test3_result unexpected kprobe_test3_result: actual 0 != expected 1
> > kprobe_multi_testmod_check:FAIL:kretprobe_test1_result unexpected kretprobe_test1_result: actual 0 != expected 1
> > kprobe_multi_testmod_check:FAIL:kretprobe_test2_result unexpected kretprobe_test2_result: actual 0 != expected 1
> > kprobe_multi_testmod_check:FAIL:kretprobe_test3_result unexpected kretprobe_test3_result: actual 0 != expected 1
> >
> >
> > Please note: this email is coming from an unmonitored mailbox. If you have
> > questions or feedback, please reach out to the Meta Kernel CI team at
> > kernel-ci@meta.com.
>
>
> --
> Masami Hiramatsu (Google) <mhiramat@kernel.org>