From: Leon Hwang <leon.hwang@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Leon Hwang <hffilwlqm@gmail.com>, Jiri Olsa <jolsa@kernel.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [BUG] Deadlock triggered by bpfsnoop funcgraph feature
Date: Mon, 1 Sep 2025 10:38:40 +0800 [thread overview]
Message-ID: <f024210f-88f6-45db-a562-4a35ec0056e7@linux.dev> (raw)
In-Reply-To: <CAADnVQL=c4B3yT18DfFP9ecgd3BL6HvnUU31Wcn0in_3+a--=g@mail.gmail.com>
On 30/8/25 02:08, Alexei Starovoitov wrote:
> On Thu, Aug 28, 2025 at 7:21 PM Leon Hwang <hffilwlqm@gmail.com> wrote:
>>
>>
>>>
>>>> Independently it would be good to make noinstr/notrace to include __cpuidle
>>>> functions. I think right now it's allowed to attach to default_idle()
>>>> which is causing issues.
>>
>> Nope.
>> ./bpfsnoop -k 'default_idle' -k '__cpuidle' --show-func-proto
>> void default_idle();
>
> hmm. indeed.
>
> Jiri,
>
> why do we still have this in selftest ?
>
> static bool skip_entry(char *name)
> {
> /*
> * We attach to almost all kernel functions and some of them
> * will cause 'suspicious RCU usage' when fprobe is attached
> * to them. Filter out the current culprits - arch_cpu_idle
> * default_idle and rcu_* functions.
> */
> if (!strcmp(name, "arch_cpu_idle"))
> return true;
> if (!strcmp(name, "default_idle"))
> return true;
After removing "arch_cpu_idle" and "default_idle", it's OK to run the
selftest:
./test_progs -t kprobe_multi_test
#155/1 kprobe_multi_test/skel_api:OK
#155/2 kprobe_multi_test/link_api_addrs:OK
#155/3 kprobe_multi_test/link_api_syms:OK
#155/4 kprobe_multi_test/attach_api_pattern:OK
#155/5 kprobe_multi_test/attach_api_addrs:OK
#155/6 kprobe_multi_test/attach_api_syms:OK
#155/7 kprobe_multi_test/attach_api_fails:OK
#155/8 kprobe_multi_test/attach_override:OK
#155/9 kprobe_multi_test/session:OK
#155/10 kprobe_multi_test/session_cookie:OK
#155/11 kprobe_multi_test/unique_match:OK
#155/12 kprobe_multi_test/kprobe_session_return_0:OK
#155/13 kprobe_multi_test/kprobe_session_return_1:OK
#155/14 kprobe_multi_test/kprobe_session_return_2:OK
#155 kprobe_multi_test:OK
#156/1 kprobe_multi_testmod_test/testmod_attach_api_syms:OK
#156/2 kprobe_multi_testmod_test/testmod_attach_api_addrs:OK
#156 kprobe_multi_testmod_test:OK
Summary: 2/16 PASSED, 0 SKIPPED, 0 FAILED
Thanks,
Leon
prev parent reply other threads:[~2025-09-01 2:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 2:13 [BUG] Deadlock triggered by bpfsnoop funcgraph feature Leon Hwang
2025-08-27 2:23 ` Alexei Starovoitov
2025-08-27 2:58 ` Leon Hwang
2025-08-28 0:42 ` Alexei Starovoitov
2025-08-28 2:40 ` Leon Hwang
2025-08-28 11:50 ` Paul E. McKenney
2025-08-28 13:39 ` Leon Hwang
2025-08-28 16:43 ` Alexei Starovoitov
2025-08-28 17:24 ` Paul E. McKenney
2025-08-29 2:21 ` Leon Hwang
2025-08-29 18:08 ` Alexei Starovoitov
2025-09-01 2:38 ` Leon Hwang [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=f024210f-88f6-45db-a562-4a35ec0056e7@linux.dev \
--to=leon.hwang@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hffilwlqm@gmail.com \
--cc=jolsa@kernel.org \
--cc=paulmck@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;
as well as URLs for NNTP newsgroup(s).