From: sashiko-bot@kernel.org
To: "Anthony Pighin" <anthony.pighin@nokia.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Don't read config space of disconnected devices in ext cap search
Date: Mon, 19 Oct 2026 16:55:39 +0000 [thread overview]
Message-ID: <sashiko-outbox-177960@kernel.org> (raw)
In-Reply-To: <20261019165159.1268120-1-anthony.pighin@nokia.com>
> Commit 4d909bf1a53e ("PCI: Refactor extended capability search into
> PCI_FIND_NEXT_EXT_CAP()") moved the extended capability search from the
> device config accessor to the bus config accessor. The bus accessor
> skips the disconnected device check, so walking the extended capability
> list of a device already marked disconnected (surprise removal, AER/DPC
> recovery) now issues real config reads to it. A dead device returns all
> ones for the first extended capability header. That decodes as a next
> pointer to the last dword of config space, so the walk keeps re-reading
> that dword until its TTL expires, roughly 480 config reads per call.
>
> Restore the device accessor so the walk stops without touching hardware
> once the device is disconnected.
>
> Fixes: 4d909bf1a53e ("PCI: Refactor extended capability search into PCI_FIND_NEXT_EXT_CAP()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Anthony Pighin <anthony.pighin@nokia.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261019165159.1268120-1-anthony.pighin@nokia.com?part=1
prev parent reply other threads:[~2026-10-19 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 16:51 [PATCH] PCI: Don't read config space of disconnected devices in ext cap search Anthony Pighin
2026-10-19 16:55 ` sashiko-bot [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=sashiko-outbox-177960@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=anthony.pighin@nokia.com \
--cc=linux-pci@vger.kernel.org \
--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.