[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <439f40a5997311fc9d750f666dcfb4a32c654a75.camel@linux.ibm.com>
Date: Tue, 20 Jan 2026 23:12:45 +0100
From: Niklas Schnelle <schnelle@...ux.ibm.com>
To: Farhan Ali <alifm@...ux.ibm.com>, linux-s390@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Cc: helgaas@...nel.org, lukas@...ner.de, alex@...zbot.org, clg@...hat.com,
stable@...r.kernel.org, mjrosato@...ux.ibm.com
Subject: Re: [PATCH v7 3/9] PCI: Avoid saving config space state if
inaccessible
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@...ux.ibm.com>
> ---
Running checkpatch.pl with "--strict" on the series it pointed out that
this commit description has lines over 75 characters.
Thanks,
Niklas
Powered by blists - more mailing lists