From: Menglong Dong <menglong8.dong@gmail.com>
To: ast@kernel.org
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, jiang.biao@linux.dev
Subject: [PATCH RFC bpf-next 3/3] selftests/bpf: add testcase for probe read fault
Date: Sat, 27 Sep 2025 14:12:10 +0800 [thread overview]
Message-ID: <20250927061210.194502-4-menglong.dong@linux.dev> (raw)
In-Reply-To: <20250927061210.194502-1-menglong.dong@linux.dev>
Add testcase for probe read fault to stream.c.
Signed-off-by: Menglong Dong <menglong.dong@linux.dev>
---
.../testing/selftests/bpf/prog_tests/stream.c | 22 ++++++++++++++++++-
tools/testing/selftests/bpf/progs/stream.c | 21 ++++++++++++++++++
2 files changed, 42 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/bpf/prog_tests/stream.c b/tools/testing/selftests/bpf/prog_tests/stream.c
index c3cce5c292bd..81fd258b97e0 100644
--- a/tools/testing/selftests/bpf/prog_tests/stream.c
+++ b/tools/testing/selftests/bpf/prog_tests/stream.c
@@ -72,7 +72,8 @@ static void test_address(struct bpf_program *prog, unsigned long *fault_addr_p)
ASSERT_OK(ret, "ret");
ASSERT_OK(opts.retval, "retval");
- sprintf(fault_addr, "0x%lx", *fault_addr_p);
+ if (fault_addr_p)
+ sprintf(fault_addr, "0x%lx", *fault_addr_p);
ret = bpf_prog_stream_read(prog_fd, BPF_STREAM_STDERR, buf, sizeof(buf), &ropts);
ASSERT_GT(ret, 0, "stream read");
@@ -106,3 +107,22 @@ void test_stream_arena_fault_address(void)
stream__destroy(skel);
}
+
+void test_stream_probe_read_fault(void)
+{
+ struct stream *skel;
+
+#if !defined(__x86_64__)
+ printf("%s:SKIP: probe fault reporting not supported\n", __func__);
+ test__skip();
+ return;
+#endif
+
+ skel = stream__open_and_load();
+ if (!ASSERT_OK_PTR(skel, "stream__open_and_load"))
+ return;
+
+ test_address(skel->progs.stream_probe_read_fault, NULL);
+
+ stream__destroy(skel);
+}
diff --git a/tools/testing/selftests/bpf/progs/stream.c b/tools/testing/selftests/bpf/progs/stream.c
index 4a5bd852f10c..290c40463522 100644
--- a/tools/testing/selftests/bpf/progs/stream.c
+++ b/tools/testing/selftests/bpf/progs/stream.c
@@ -7,6 +7,8 @@
#include "bpf_experimental.h"
#include "bpf_arena_common.h"
+#define READ_ONCE(x) (*(volatile typeof(x) *)&(x))
+
struct arr_elem {
struct bpf_res_spin_lock lock;
};
@@ -234,4 +236,23 @@ int stream_arena_callback_fault(void *ctx)
return 0;
}
+SEC("syscall")
+__arch_x86_64
+__success __retval(0)
+__stderr("ERROR: Probe READ access faule, insn=0x[0-9a-fA-F]+")
+__stderr("CPU: {{[0-9]+}} UID: 0 PID: {{[0-9]+}} Comm: {{.*}}")
+__stderr("Call trace:\n"
+"{{([a-zA-Z_][a-zA-Z0-9_]*\\+0x[0-9a-fA-F]+/0x[0-9a-fA-F]+\n"
+"|[ \t]+[^\n]+\n)*}}")
+int stream_probe_read_fault(void *ctx)
+{
+ struct sk_buff *skb = bpf_core_cast((void *)0xFFFFFFFF00000000,
+ struct sk_buff);
+
+ /* do the memory read */
+ READ_ONCE(skb->network_header);
+
+ return 0;
+}
+
char _license[] SEC("license") = "GPL";
--
2.51.0
prev parent reply other threads:[~2025-09-27 6:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 6:12 [PATCH RFC bpf-next 0/3] bpf: report probe fault to BPF stderr Menglong Dong
2025-09-27 6:12 ` [PATCH RFC bpf-next 1/3] " Menglong Dong
2025-10-02 2:03 ` Alexei Starovoitov
2025-10-07 6:14 ` Menglong Dong
2025-10-08 14:40 ` Leon Hwang
2025-10-08 16:27 ` bpf_errno. Was: " Alexei Starovoitov
2025-10-08 17:08 ` Kumar Kartikeya Dwivedi
2025-10-08 19:34 ` Eduard Zingerman
2025-10-08 20:08 ` Kumar Kartikeya Dwivedi
2025-10-08 20:30 ` Eduard Zingerman
2025-10-08 20:59 ` Kumar Kartikeya Dwivedi
2025-10-09 14:29 ` Leon Hwang
2025-10-09 15:15 ` Leon Hwang
2025-10-10 12:05 ` Menglong Dong
2025-10-10 15:10 ` Menglong Dong
2025-10-10 18:55 ` Eduard Zingerman
2025-10-11 1:23 ` Menglong Dong
2025-10-09 14:15 ` Leon Hwang
2025-10-09 14:45 ` Alexei Starovoitov
2025-10-10 14:22 ` Leon Hwang
2025-09-27 6:12 ` [PATCH RFC bpf-next 2/3] x86,bpf: use bpf_prog_report_probe_violation for x86 Menglong Dong
2025-09-27 6:12 ` Menglong Dong [this message]
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=20250927061210.194502-4-menglong.dong@linux.dev \
--to=menglong8.dong@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=jiang.biao@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®