From: sashiko-bot@kernel.org
To: "Haoran Wang" <haoranwangsec@gmail.com>
Cc: linux-rt-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] libcxgb: use raw_cpu_ptr() in ppm_get_cpu_entries()
Date: Wed, 11 Nov 2026 08:58:00 +0000 [thread overview]
Message-ID: <sashiko-outbox-208645@kernel.org> (raw)
In-Reply-To: <20261110165742.1204-1-haoranwangsec@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] libcxgb: missing Fixes: trailer on bug-fix commit for
ppm_get_cpu_entries()
--
commit 5481811981b3771bf6244d1b3e3e8e9871700ea8
Author: Haoran Wang <haoranwangsec@gmail.com>
> libcxgb: use raw_cpu_ptr() in ppm_get_cpu_entries()
>
> ppm_get_cpu_entries() must not acquire a sleeping lock while preemption
> is disabled: get_cpu() raises preempt_count and spin_lock_bh() may sleep
> on PREEMPT_RT kernels. Read the current CPU with raw_cpu_ptr() instead,
> which keeps the per-CPU accessor stable without disabling preemption.
>
> Using the pool of a CPU the thread has since migrated away from is
> harmless: the per-CPU pools are shards of the global ppod index space,
> and the free path ppm_unmark_entries() derives the owning pool from the
> index instead of from the running CPU, so any thread can service any
> shard. Derive the global index base from pool->base so it always
> matches the pool that was locked.
>
> Signed-off-by: Haoran Wang <haoranwangsec@gmail.com>
[Severity: Low]
Since this fixes a sleeping-while-atomic bug on PREEMPT_RT in
ppm_get_cpu_entries(), should it include a Fixes: tag?
Fixes: 47da7e62b391 ("cxgb4: add iSCSI DDP page pod manager")
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261110165742.1204-1-haoranwangsec@gmail.com?part=1
next prev parent reply other threads:[~2026-11-11 8:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 13:22 [PATCH] libcxgb: use raw_cpu_ptr() in ppm_get_cpu_entries() Haoran Wang
2026-10-19 13:29 ` netdev-bot+sinfo
2026-10-19 13:29 ` Sebastian Andrzej Siewior
2026-10-20 13:22 ` sashiko-bot
2026-10-22 7:25 ` netdev-bot+sashiko
[not found] ` <CANZ3JQQrrntu0TefPZC79pKSmsOfwAngRJyuaVm81DYaJNFHFQ@mail.gmail.com>
2026-11-09 10:07 ` [PATCH v3] " Haoran Wang
2026-11-09 10:11 ` netdev-bot+sinfo
2026-11-09 20:03 ` David Laight
2026-11-10 8:57 ` [PATCH v4] " Haoran Wang
2026-11-10 9:02 ` netdev-bot+sinfo
2026-11-11 8:58 ` sashiko-bot [this message]
2026-11-11 12:17 ` Sebastian Andrzej Siewior
2026-11-12 2:59 ` netdev-bot+sashiko
2026-11-10 10:08 ` [PATCH v3] " sashiko-bot
2026-11-11 16:08 ` netdev-bot+sashiko
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=sashiko-outbox-208645@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=haoranwangsec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=sashiko-reviews@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.