From: Eduard Zingerman <eddyz87@gmail.com>
To: Ning Ding <dingning04@gmail.com>, bpf@vger.kernel.org
Cc: memxor@gmail.com, puranjay@kernel.org, paulmck@kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>,
Emil Tsalapatis <emil@etsalapatis.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next 1/2] bpf: Account for preempt and IRQ state in RCU protection
Date: Mon, 10 Aug 2026 12:30:53 -0700 [thread overview]
Message-ID: <a3c4305c694a07aa020f4b0f0e4fe7f58672b5cd.camel@gmail.com> (raw)
In-Reply-To: <20260805233940.3966981-2-dingning04@gmail.com>
On Wed, 2026-08-05 at 16:39 -0700, Ning Ding wrote:
> Disabling preemption or local IRQs keeps the current CPU in an RCU
> read-side critical section, but in_rcu_cs() does not account for either
> state. The verifier therefore rejects safe kptr accesses and invalidates
> pointers when another RCU source ends.
>
> Include preemption-disabled and IRQ-disabled state in in_rcu_cs().
> Invalidate RCU-protected pointers on RCU unlock, preempt enable, or IRQ
> restore only after the final protection ends.
>
> Signed-off-by: Ning Ding <dingning04@gmail.com>
> ---
Hi Ning,
Thank you for identifying and fixing this issue!
Acked-by: Eduard Zingerman <eddyz87@gmail.com>
...
next prev parent reply other threads:[~2026-08-10 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260805233940.3966981-1-dingning04@gmail.com>
2026-08-05 23:39 ` Ning Ding
2026-08-10 19:30 ` Eduard Zingerman [this message]
2026-08-10 19:33 ` Eduard Zingerman
2026-08-05 23:39 ` [PATCH bpf-next 2/2] selftests/bpf: Test overlapping " Ning Ding
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=a3c4305c694a07aa020f4b0f0e4fe7f58672b5cd.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dingning04@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=paulmck@kernel.org \
--cc=puranjay@kernel.org \
--cc=song@kernel.org \
--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
all inboxes | Powered by JetHome®