From: Lukas Wunner <lukas@wunner.de>
To: sashiko-reviews@lists.linux.dev
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH 3/7] PCI/ERR: Avoid stale error status bits on recovery failure
Date: Sun, 27 Sep 2026 20:57:27 +0200 [thread overview]
Message-ID: <arlnF7FsstceeiZ5@wunner.de> (raw)
In-Reply-To: <20260927183122.8B3F91F000FF@smtp.kernel.org>
On Sun, Sep 27, 2026 at 06:31:22PM +0000, sashiko-bot@kernel.org wrote:
> > +++ b/drivers/pci/pcie/err.c
> > @@ -284,6 +284,11 @@ pci_ers_result_t pcie_do_recovery(struct pci_dev *dev,
> > return status;
> >
> > failed:
> > + if (host->native_aer || pcie_ports_native) {
> > + pcie_clear_device_status(dev);
> > + pci_aer_clear_nonfatal_status(dev);
>
> [Severity: Medium]
> When pcie_do_recovery() is invoked for a fatal error (pci_channel_io_frozen)
> and recovery fails, will this leave the fatal error bits uncleared?
Generally not.
First of all, the error status bits in the Device Status register are
cleared because in the "pci_channel_io_frozen" case, a reset is performed
unconditionally. (They are not sticky, i.e. they do not survive a reset.)
Second, the Uncorrectable Error Status register is cleared as well because
the first thing that a driver's ->slot_reset() callback does is generally
a call to pci_restore_state(), which calls pci_aer_clear_status().
Hence explicitly clearing error status bits in the Fatal Error case has
historically been considered unnecessary. That said, I'm not happy with
how the bits are cleared and consider this patch an interim solution.
In the long run, I would like to clear error bits immediately when a
device is examined in is_error_source() and aer_get_device_error_info(),
and I would like to clear only those bits that have been read.
Right now we may lose error bits that occur in-between reading the register
and later-on clearing it, so this is all somewhat suboptimal.
Thanks,
Lukas
next prev parent reply other threads:[~2026-09-27 18:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 18:02 [PATCH 0/7] Error reporting for AER-incapable devices Lukas Wunner
2026-09-27 18:02 ` [PATCH 1/7] PCI/DPC: Avoid access to non-existent AER capability Lukas Wunner
2026-09-27 18:27 ` sashiko-bot
2026-09-29 18:49 ` Kuppuswamy Sathyanarayanan
2026-09-27 18:02 ` [PATCH 2/7] PCI/DPC: Reinstate support for AER-incapable ports Lukas Wunner
2026-09-27 18:26 ` sashiko-bot
2026-09-29 19:04 ` Kuppuswamy Sathyanarayanan
2026-09-27 18:02 ` [PATCH 3/7] PCI/ERR: Avoid stale error status bits on recovery failure Lukas Wunner
2026-09-27 18:31 ` sashiko-bot
2026-09-27 18:57 ` Lukas Wunner [this message]
2026-09-29 19:20 ` Kuppuswamy Sathyanarayanan
2026-09-27 18:02 ` [PATCH 4/7] PCI/AER: Drop AER native check from handles_cxl_errors() Lukas Wunner
2026-09-27 18:26 ` sashiko-bot
2026-09-28 20:58 ` Bowman, Terry
2026-09-29 19:24 ` Kuppuswamy Sathyanarayanan
2026-09-27 18:02 ` [PATCH 5/7] PCI/AER: Move AER capability check out of pcie_aer_is_native() Lukas Wunner
2026-09-27 18:30 ` sashiko-bot
2026-09-29 19:47 ` Kuppuswamy Sathyanarayanan
2026-09-27 18:02 ` [PATCH 6/7] PCI/AER: Renumber severity constants Lukas Wunner
2026-09-27 18:29 ` sashiko-bot
2026-09-27 19:23 ` Lukas Wunner
2026-09-29 19:55 ` Kuppuswamy Sathyanarayanan
2026-09-27 18:02 ` [PATCH 7/7] PCI/AER: Enable baseline capability error reporting Lukas Wunner
2026-09-27 18:33 ` sashiko-bot
2026-09-29 21:01 ` Kuppuswamy Sathyanarayanan
2026-09-30 7:08 ` Lukas Wunner
2026-10-01 17:44 ` Kuppuswamy Sathyanarayanan
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=arlnF7FsstceeiZ5@wunner.de \
--to=lukas@wunner.de \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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