diff options
| author | Niklas Schnelle <schnelle@linux.ibm.com> | 2024-04-11 14:01:39 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-11-01 01:58:19 +0100 |
| commit | b56328660be084d200e946a4141e4321762bb89f (patch) | |
| tree | 8d3ce2175a3f4aa097e3842742e55090f69db8ce /kernel | |
| parent | 6617ae800cbb210d93970ce4102f4c1b4ab34103 (diff) | |
| download | linux-b56328660be084d200e946a4141e4321762bb89f.tar.gz linux-b56328660be084d200e946a4141e4321762bb89f.tar.bz2 linux-b56328660be084d200e946a4141e4321762bb89f.zip | |
s390/pci: Handle PCI error codes other than 0x3a
[ Upstream commit 3cd03ea57e8e16cc78cc357d5e9f26078426f236 ]
The Linux implementation of PCI error recovery for s390 was based on the
understanding that firmware error recovery is a two step process with an
optional initial error event to indicate the cause of the error if known
followed by either error event 0x3A (Success) or 0x3B (Failure) to
indicate whether firmware was able to recover. While this has been the
case in testing and the error cases seen in the wild it turns out this
is not correct. Instead firmware only generates 0x3A for some error and
service scenarios and expects the OS to perform recovery for all PCI
events codes except for those indicating permanent error (0x3B, 0x40)
and those indicating errors on the function measurement block (0x2A,
0x2B, 0x2C). Align Linux behavior with these expectations.
Fixes: 4cdf2f4e24ff ("s390/pci: implement minimal PCI error recovery")
Reviewed-by: Gerd Bayer <gbayer@linux.ibm.com>
Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com>
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions