From: Lukas Wunner <lukas@wunner.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Breno Leitao <leitao@debian.org>,
Jonathan Corbet <corbet@lwn.net>,
Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
Oliver O'Halloran <oohall@gmail.com>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org,
dcostantino@meta.com, rneu@meta.com, kernel-team@meta.com
Subject: Re: [PATCH] PCI/AER: Add option to panic on unrecoverable errors
Date: Fri, 6 Feb 2026 22:10:48 +0100 [thread overview]
Message-ID: <aYZY2KgtSnqUWXbu@wunner.de> (raw)
In-Reply-To: <aYZU09qCN3u-_byj@wunner.de>
On Fri, Feb 06, 2026 at 09:53:39PM +0100, Lukas Wunner wrote:
> So I wouldn't consider 918b4053184c to have been a universally successful
> approach and I fear that this patch goes even further.
Forgot to mention -- there's another problem:
PCI_ERS_RESULT_NO_AER_DRIVER is obviously AER-specific.
powerpc (EEH) and s390 have error recovery mechanisms separate from AER
and we've been trying to align them more closely so that drivers don't
need to be aware of platform-specific behavior.
eeh_pe_report_edev() does not modify the pci_ers_result for unbound
drivers and those without pci_error_handlers. And the default is
PCI_ERS_RESULT_NONE. eeh_report_error() also returns PCI_ERS_RESULT_NONE
for drivers without ->error_detected() callback.
In the PCI_ERS_RESULT_NONE case, EEH seems to perform a reset and
assume successful recovery.
It's only AER that is this strict about unbound devices and drivers that
lack pci_error_handlers.
If anything we should try to *reduce* deviations between the various
error recovery mechanisms, not double down on increasing them.
Thanks,
Lukas
next prev parent reply other threads:[~2026-02-06 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 18:23 [PATCH] PCI/AER: Add option to panic on unrecoverable errors Breno Leitao
2026-02-06 18:41 ` Lukas Wunner
2026-02-06 18:50 ` Keith Busch
2026-02-06 18:52 ` Bjorn Helgaas
2026-02-06 19:22 ` Keith Busch
2026-02-06 20:53 ` Lukas Wunner
2026-02-06 21:10 ` Lukas Wunner [this message]
2026-02-07 5:55 ` Keith Busch
2026-02-09 14:28 ` Breno Leitao
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=aYZY2KgtSnqUWXbu@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=dcostantino@meta.com \
--cc=helgaas@kernel.org \
--cc=kbusch@kernel.org \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=rneu@meta.com \
/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