From: Jiri Olsa <olsajiri@gmail.com>
To: Varun R Mallya <varunrmallya@gmail.com>
Cc: bpf@vger.kernel.org, leon.hwang@linux.dev, memxor@gmail.com,
ast@kernel.org, daniel@iogearbox.net, yonghong.song@linux.dev,
rostedt@goodmis.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 2/2] selftests/bpf: Add test to ensure kprobe_multi is not sleepable
Date: Wed, 8 Apr 2026 22:13:33 +0200 [thread overview]
Message-ID: <ada27R-ai8FvnPu0@krava> (raw)
In-Reply-To: <adai2mXaRGpf1Kvb@computer>
On Thu, Apr 09, 2026 at 12:17:54AM +0530, Varun R Mallya wrote:
> On Thu, Apr 09, 2026 at 12:05:49AM +0530, Varun R Mallya wrote:
> > @@ -676,5 +750,7 @@ void test_kprobe_multi_test(void)
> > test_unique_match();
> > if (test__start_subtest("attach_write_ctx"))
> > test_attach_write_ctx();
> > + if (test__start_subtest("attach_multi_sleepable"))
> > + test_attach_multi_sleepable();
> > RUN_TESTS(kprobe_multi_verifier);
> Please ignore this patch. I will send a v5 in a few minutes. I forgot to
> remove the selftest from the previous location after moving it into
> attach_api_fails.
also no need to send patch#1 it's already in:
eb7024bfcc5f bpf: Reject sleepable kprobe_multi programs at attach time
jirka
> > +}
> > +
> > +char _license[] SEC("license") = "GPL";
> > --
> > 2.53.0
> >
prev parent reply other threads:[~2026-04-08 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 18:35 [PATCH bpf-next v4 0/2] Reject sleepable kprobe_multi programs at attach time Varun R Mallya
2026-04-08 18:35 ` [PATCH bpf-next v4 1/2] bpf: " Varun R Mallya
2026-04-08 18:35 ` [PATCH bpf-next v4 2/2] selftests/bpf: Add test to ensure kprobe_multi is not sleepable Varun R Mallya
2026-04-08 18:47 ` Varun R Mallya
2026-04-08 20:13 ` Jiri Olsa [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=ada27R-ai8FvnPu0@krava \
--to=olsajiri@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=rostedt@goodmis.org \
--cc=varunrmallya@gmail.com \
--cc=yonghong.song@linux.dev \
/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