public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
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,
	julianr@linux.ibm.com
Subject: Re: [PATCH v8 3/9] PCI: Avoid saving config space state if inaccessible
Date: Mon, 26 Jan 2026 22:00:10 +0100	[thread overview]
Message-ID: <344d4e1c57d2eeb750b0c0edf12d88eb31e05ed0.camel@linux.ibm.com> (raw)
In-Reply-To: <20260122194437.1903-4-alifm@linux.ibm.com>

On Thu, 2026-01-22 at 11:44 -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 | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index c105e285cff8..e7beaf1f65a7 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;

Nit: I believe the PCI subsystem prefers reverse X-mas tree
declarations

>  	const struct pci_error_handlers *err_handler =
>  			dev->driver ? dev->driver->err_handler : NULL;
>  
> @@ -4980,6 +4981,19 @@ static void pci_dev_save_and_disable(struct pci_dev *dev)
>  	 */
>  	pci_set_power_state(dev, PCI_D0);
>  
> +	/*
> +	 * If device's config space is inaccessible it can return ~0 for
> +	 * any reads. Since VFs can also return ~0 for Device and Vendor ID
> +	 * check Command and Status registers. At the very least we should
> +	 * avoid restoring config space for device with error bits set in
> +	 * Status register.
> +	 */
> +	pci_read_config_dword(dev, PCI_COMMAND, &val);
> +	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

Looks good to me thanks! Feel free to add:

Reviewed-by: Niklas Schnelle <schnelle@linux.ibm.com>

  reply	other threads:[~2026-01-26 21:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 19:44 [PATCH v8 0/9] Error recovery for vfio-pci devices on s390x Farhan Ali
2026-01-22 19:44 ` [PATCH v8 1/9] PCI: Allow per function PCI slots Farhan Ali
2026-01-22 19:44 ` [PATCH v8 2/9] s390/pci: Add architecture specific resource/bus address translation Farhan Ali
2026-01-22 19:44 ` [PATCH v8 3/9] PCI: Avoid saving config space state if inaccessible Farhan Ali
2026-01-26 21:00   ` Niklas Schnelle [this message]
2026-02-07  0:39   ` Bjorn Helgaas
2026-02-09 18:20     ` Farhan Ali
2026-01-22 19:44 ` [PATCH v8 4/9] PCI: Add additional checks for flr reset Farhan Ali
2026-01-26 13:11   ` Julian Ruess
2026-01-22 19:44 ` [PATCH v8 5/9] s390/pci: Update the logic for detecting passthrough device Farhan Ali
2026-01-22 19:44 ` [PATCH v8 6/9] s390/pci: Store PCI error information for passthrough devices Farhan Ali
2026-01-22 19:44 ` [PATCH v8 7/9] vfio-pci/zdev: Add a device feature for error information Farhan Ali
2026-01-27 10:53   ` Niklas Schnelle
2026-01-27 21:44     ` Farhan Ali
2026-01-22 19:44 ` [PATCH v8 8/9] vfio: Add a reset_done callback for vfio-pci driver Farhan Ali
2026-01-27 11:02   ` Niklas Schnelle
2026-01-22 19:44 ` [PATCH v8 9/9] vfio: Remove the pcie check for VFIO_PCI_ERR_IRQ_INDEX Farhan Ali
2026-01-26 15:31   ` Julian Ruess
2026-01-26 17:38     ` Farhan Ali
2026-01-27  8:15   ` Julian Ruess
2026-01-27 11:16   ` Niklas Schnelle
2026-02-06 19:03 ` [PATCH v8 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=344d4e1c57d2eeb750b0c0edf12d88eb31e05ed0.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=julianr@linux.ibm.com \
    --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