From: sashiko-bot@kernel.org
To: "Farhan Ali" <alifm@linux.ibm.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v15 3/7] PCI: Fail FLR when config space is inaccessible
Date: Tue, 05 May 2026 22:20:18 +0000 [thread overview]
Message-ID: <20260505222018.9CAC9C2BCB4@smtp.kernel.org> (raw)
In-Reply-To: <20260505200510.2954-4-alifm@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Logic flaw: pci_dev_config_accessible() executed before the probe check can permanently disable the FLR capability.
--
commit dc74511c4dd4719d1b362bacdaab4c551ada9e66
Author: Farhan Ali <alifm@linux.ibm.com>
PCI: Fail FLR when config space is inaccessible
This commit adds a check to validate if a device's config space is accessible
before attempting an FLR reset. This is intended to fail the FLR early when
the device is in an error state.
> If a device is in an error state, then it's config space may not be
> accssible.
This isn't a bug, but there are a couple of typos here ("it's" instead of
"its", and "accssible" instead of "accessible").
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index e71b814153921..c50418f5e3181 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -4396,6 +4396,9 @@ int pcie_reset_flr(struct pci_dev *dev, bool probe)
> if (!(dev->devcap & PCI_EXP_DEVCAP_FLR))
> return -ENOTTY;
>
> + if (!pci_dev_config_accessible(dev, "FLR"))
> + return -ENOTTY;
> +
> if (probe)
> return 0;
Could this placement cause the FLR capability to be permanently disabled if
the device is temporarily inaccessible during discovery?
pcie_reset_flr() is called with probe == true during device initialization
to discover if the hardware inherently supports FLR. By placing the live
config space check before the probe check, the system will actively read the
PCI_COMMAND register during capability discovery.
If the device happens to be temporarily inaccessible during this probe phase,
it will return -ENOTTY and FLR will be permanently omitted from the device's
reset_methods array.
Would it make sense to move the pci_dev_config_accessible() check after the
if (probe) block so we only check accessibility when actually performing the
reset?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260505200510.2954-1-alifm@linux.ibm.com?part=3
next prev parent reply other threads:[~2026-05-05 22:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 20:05 [PATCH v15 0/7] Error recovery for vfio-pci devices on s390x Farhan Ali
2026-05-05 20:05 ` [PATCH v15 1/7] PCI: Allow per function PCI slots to fix slot reset on s390 Farhan Ali
2026-05-05 21:29 ` sashiko-bot
2026-05-05 20:05 ` [PATCH v15 2/7] PCI: Avoid saving config space state if inaccessible Farhan Ali
2026-05-05 21:58 ` sashiko-bot
2026-05-05 20:05 ` [PATCH v15 3/7] PCI: Fail FLR when config space is inaccessible Farhan Ali
2026-05-05 22:20 ` sashiko-bot [this message]
2026-05-05 20:05 ` [PATCH v15 4/7] s390/pci: Store PCI error information for passthrough devices Farhan Ali
2026-05-05 22:56 ` sashiko-bot
2026-05-06 9:38 ` Niklas Schnelle
2026-05-06 17:20 ` Farhan Ali
2026-05-08 19:58 ` Niklas Schnelle
2026-05-05 20:05 ` [PATCH v15 5/7] vfio-pci/zdev: Add a device feature for error information Farhan Ali
2026-05-05 23:27 ` sashiko-bot
2026-05-05 20:05 ` [PATCH v15 6/7] vfio/pci: Add a reset_done callback for vfio-pci driver Farhan Ali
2026-05-05 23:56 ` sashiko-bot
2026-05-05 20:05 ` [PATCH v15 7/7] vfio/pci: Remove the pcie check for VFIO_PCI_ERR_IRQ_INDEX Farhan Ali
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=20260505222018.9CAC9C2BCB4@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alifm@linux.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox