From: patchwork-bot+netdevbpf@kernel.org
To: Sahil Chandna <chandna.sahil@gmail.com>
Cc: yonghong.song@linux.dev, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
bigeasy@linutronix.de, bpf@vger.kernel.org,
syzbot+b0cff308140f79a9c4cb@syzkaller.appspotmail.com
Subject: Re: [PATCH bpf-next v3] bpf: prevent nesting overflow in bpf_try_get_buffers
Date: Fri, 14 Nov 2025 21:10:09 +0000 [thread overview]
Message-ID: <176315460900.1836273.4880914220928458994.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251114064922.11650-1-chandna.sahil@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 14 Nov 2025 12:19:22 +0530 you wrote:
> bpf_try_get_buffers() returns one of multiple per-CPU buffers based on a
> per-CPU nesting counter. This mechanism expects that buffers are not
> endlessly acquired before being returned. migrate_disable() ensures that a
> task remains on the same CPU, but it does not prevent the task from being
> preempted by another task on that CPU.
>
> Without disabled preemption, a task may be preempted while holding a
> buffer, allowing another task to run on same CPU and acquire an
> additional buffer. Several such preemptions can cause the per-CPU
> nest counter to exceed MAX_BPRINTF_NEST_LEVEL and trigger the warning in
> bpf_try_get_buffers(). Adding preempt_disable()/preempt_enable() around
> buffer acquisition and release prevents this task preemption and
> preserves the intended bounded nesting behavior.
>
> [...]
Here is the summary with links:
- [bpf-next,v3] bpf: prevent nesting overflow in bpf_try_get_buffers
https://git.kernel.org/bpf/bpf-next/c/c1da3df7191f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-14 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 6:49 [PATCH bpf-next v3] bpf: prevent nesting overflow in bpf_try_get_buffers Sahil Chandna
2025-11-14 21:10 ` patchwork-bot+netdevbpf [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=176315460900.1836273.4880914220928458994.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bpf@vger.kernel.org \
--cc=chandna.sahil@gmail.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=syzbot+b0cff308140f79a9c4cb@syzkaller.appspotmail.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