From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Farhan Ali <alifm@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Cc: helgaas@kernel.org, lukas@wunner.de, alex@shazbot.org,
clg@redhat.com, stable@vger.kernel.org, mjrosato@linux.ibm.com
Subject: Re: [PATCH v7 3/9] PCI: Avoid saving config space state if inaccessible
Date: Mon, 19 Jan 2026 22:23:55 +0100 [thread overview]
Message-ID: <abbebb0fa74a854e8c794a01659bad2583b87dc8.camel@linux.ibm.com> (raw)
In-Reply-To: <20260107183217.1365-4-alifm@linux.ibm.com>
On Wed, 2026-01-07 at 10:32 -0800, Farhan Ali wrote:
> The current reset process saves the device's config space state before reset
> and restores it afterward. However errors may occur unexpectedly and it may
> then be impossible to save config space because the device may be inaccessible
> (e.g. DPC) or config space may be corrupted. This results in saving corrupted
> values that get written back to the device during state restoration.
>
> With a reset we want to recover/restore the device into a functional
> state. So avoid saving the state of the config space when the device config
> space is inaccessible.
>
> Signed-off-by: Farhan Ali <alifm@linux.ibm.com>
> ---
> drivers/pci/pci.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index c105e285cff8..74d21c97654d 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -4960,6 +4960,7 @@ EXPORT_SYMBOL_GPL(pci_dev_unlock);
>
> static void pci_dev_save_and_disable(struct pci_dev *dev)
> {
> + u32 val;
> const struct pci_error_handlers *err_handler =
> dev->driver ? dev->driver->err_handler : NULL;
>
> @@ -4980,6 +4981,12 @@ static void pci_dev_save_and_disable(struct pci_dev *dev)
> */
> pci_set_power_state(dev, PCI_D0);
>
> + pci_read_config_dword(dev, PCI_COMMAND, &val);
Since the PCI_COMMAND field is only 16 bits I think it warrants a
comment that you're reading both PCI_COMMAND and PCI_STATUS and that
both together should never be 0xffffffff and why. I think at least
PCI_STATUS_PARITY should never be set in a config space we want to
restore.
> + if (PCI_POSSIBLE_ERROR(val)) {
> + pci_warn(dev, "Device config space inaccessible\n");
> + return;
> + }
> +
> pci_save_state(dev);
> /*
> * Disable the device by clearing the Command register, except for
Functionally this looks good to me and I agree that with both DPC and
s390x PCI error state behavior this makes sense.
Thanks,
Niklas
next prev parent reply other threads:[~2026-01-19 21:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 18:32 [PATCH v7 0/9] Error recovery for vfio-pci devices on s390x Farhan Ali
2026-01-07 18:32 ` [PATCH v7 1/9] PCI: Allow per function PCI slots Farhan Ali
2026-01-07 18:32 ` [PATCH v7 2/9] s390/pci: Add architecture specific resource/bus address translation Farhan Ali
2026-01-20 22:15 ` Niklas Schnelle
2026-01-07 18:32 ` [PATCH v7 3/9] PCI: Avoid saving config space state if inaccessible Farhan Ali
2026-01-19 21:23 ` Niklas Schnelle [this message]
2026-01-20 19:50 ` Farhan Ali
2026-01-20 22:12 ` Niklas Schnelle
2026-01-07 18:32 ` [PATCH v7 4/9] PCI: Add additional checks for flr reset Farhan Ali
2026-01-19 21:34 ` Niklas Schnelle
2026-01-07 18:32 ` [PATCH v7 5/9] s390/pci: Update the logic for detecting passthrough device Farhan Ali
2026-01-07 18:32 ` [PATCH v7 6/9] s390/pci: Store PCI error information for passthrough devices Farhan Ali
2026-01-20 22:34 ` Niklas Schnelle
2026-01-07 18:32 ` [PATCH v7 7/9] vfio-pci/zdev: Add a device feature for error information Farhan Ali
2026-01-19 16:24 ` Julian Ruess
2026-01-20 18:54 ` Farhan Ali
2026-01-07 18:32 ` [PATCH v7 8/9] vfio: Add a reset_done callback for vfio-pci driver Farhan Ali
2026-01-19 16:41 ` Julian Ruess
2026-01-07 18:32 ` [PATCH v7 9/9] vfio: Remove the pcie check for VFIO_PCI_ERR_IRQ_INDEX Farhan Ali
2026-01-19 16:56 ` Julian Ruess
2026-01-20 18:56 ` Farhan Ali
2026-01-15 18:28 ` [PATCH v7 0/9] Error recovery for vfio-pci devices on s390x 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=abbebb0fa74a854e8c794a01659bad2583b87dc8.camel@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=alex@shazbot.org \
--cc=alifm@linux.ibm.com \
--cc=clg@redhat.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mjrosato@linux.ibm.com \
--cc=stable@vger.kernel.org \
/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