From: Paolo Abeni <pabeni@redhat.com>
To: "Nikhil P. Rao" <nikhil.rao@amd.com>, netdev@vger.kernel.org
Cc: kuba@kernel.org, brett.creeley@amd.com, eric.joyner@amd.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com
Subject: Re: [PATCH net] pds_core: fix cmd_regs access racing BAR unmap on reset
Date: Tue, 4 Aug 2026 12:26:54 +0200 [thread overview]
Message-ID: <917affb8-f750-4e11-aade-e4ebf13e96ce@redhat.com> (raw)
In-Reply-To: <20260729055258.1416225-1-nikhil.rao@amd.com>
On 7/29/26 7:52 AM, Nikhil P. Rao wrote:
> pdsc_reset_prepare() and pdsc_reset_done()'s pdsc_map_bars() error path
> clear/iounmap cmd_regs without devcmd_lock, and pdsc_firmware_update()'s
> download loop derefs cmd_regs after dropping and retaking the lock
> without re-checking. An FLR concurrent with a devlink flash can unmap
> cmd_regs under an in-flight devcmd, causing a NULL deref or a write to
> unmapped MMIO.
>
> Take devcmd_lock across the BAR unmap/remap. Only the PF maps cmd_regs
> and runs devcmd, so guard the locking to the PF.
>
> pdsc_unmap_bars() also clears info_regs, which has its own readers under
> config_lock (and a lockless debugfs reader); that teardown race is
> pre-existing and handled separately.
>
> Fixes: e96094c1d11c ("pds_core: Clear BARs on reset")
> Reported-by: sashiko-bot <sashiko-bot@kernel.org>
> Closes: https://sashiko.dev/#/patchset/20260708212222.296202-1-nikhil.rao%40amd.com?part=3
> Assisted-by: Claude:claude-opus-4.8
> Signed-off-by: Nikhil P. Rao <nikhil.rao@amd.com>
> ---
> drivers/net/ethernet/amd/pds_core/fw.c | 6 ++++++
> drivers/net/ethernet/amd/pds_core/main.c | 10 +++++++++-
> 2 files changed, 15 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/amd/pds_core/fw.c b/drivers/net/ethernet/amd/pds_core/fw.c
> index fa626719e68d..cd7616ed9ef3 100644
> --- a/drivers/net/ethernet/amd/pds_core/fw.c
> +++ b/drivers/net/ethernet/amd/pds_core/fw.c
> @@ -134,6 +134,12 @@ int pdsc_firmware_update(struct pdsc *pdsc, const struct firmware *fw,
>
> copy_sz = min_t(unsigned int, buf_sz, fw->size - offset);
> mutex_lock(&pdsc->devcmd_lock);
> + if (!pdsc->cmd_regs) {
Sashiko notes this is still racy:
https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260729055258.1416225-1-nikhil.rao%40amd.com
The issue is marked as a pre-existing one, but IMHO is so strictly
related that deserve fixing in the same change.
/P
next prev parent reply other threads:[~2026-08-04 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 5:52 [PATCH net] pds_core: fix cmd_regs access racing BAR unmap on reset Nikhil P. Rao
2026-08-04 10:26 ` Paolo Abeni [this message]
2026-08-05 0:28 ` Rao, Nikhil
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=917affb8-f750-4e11-aade-e4ebf13e96ce@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.joyner@amd.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikhil.rao@amd.com \
/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