From: patchwork-bot+netdevbpf@kernel.org
To: Hui Su <sh_def@163.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
song@kernel.org, martin.lau@linux.dev, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] bpf: Fix infinite loop in pcpu_freelist push with one possible CPU
Date: Thu, 20 Aug 2026 18:50:08 +0000 [thread overview]
Message-ID: <178725180892.429815.3721455388690610183.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260806175600.1993595-1-sh_def@163.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Fri, 7 Aug 2026 01:56:00 +0800 you wrote:
> __pcpu_freelist_push() can loop forever when only one CPU is possible
> and an NMI re-enters pcpu_freelist_push() while the interrupted context
> holds that CPU's freelist lock.
>
> After the current-CPU fast path fails, the fallback loop walks
> cpu_possible_mask while skipping the current CPU. With CONFIG_SMP=n, or
> when an SMP kernel is limited to one possible CPU with nr_cpus=1 or
> possible_cpus=1, there are no other possible CPUs to examine. The loop
> therefore makes no lock acquisition attempt and can never make progress.
>
> [...]
Here is the summary with links:
- bpf: Fix infinite loop in pcpu_freelist push with one possible CPU
https://git.kernel.org/bpf/bpf/c/efebf6496685
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:[~2026-08-20 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 17:56 [PATCH] bpf: Fix infinite loop in pcpu_freelist push with one possible CPU Hui Su
2026-08-20 18:50 ` 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=178725180892.429815.3721455388690610183.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=sh_def@163.com \
--cc=song@kernel.org \
--cc=stable@vger.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