From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <helgaas@kernel.org>, linux-pci@vger.kernel.org
Cc: Sourabh Jain <sourabhjain@linux.ibm.com>,
Oliver OHalloran <oohall@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
Alex Deucher <alexander.deucher@amd.com>,
Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Keith Busch <kbusch@kernel.org>,
Maciej Grochowski <Maciej.Grochowski@sony.com>
Subject: [PATCH 0/2] PCI/AER: Improve Error Source handling
Date: Tue, 3 Nov 2026 10:45:00 +0100 [thread overview]
Message-ID: <cover.1793697480.git.lukas@wunner.de> (raw)
While analyzing log output provided by Alex, I noticed that the AER driver
fails to find the error-signaling device if the Error Source ID register
contains an invalid, non-zero value. Patch [2/2] fixes that.
Also, a potential NULL pointer deref caught my eye in that portion of the
code which is fixed by patch [1/2]. I believe this is hard to trigger,
but the kernel should still handle it gracefully.
Lukas Wunner (2):
PCI/AER: Avoid NULL pointer deref on search for Error Source
PCI/AER: Check validity of Error Source ID register
drivers/pci/pci.h | 7 ++++++-
drivers/pci/pcie/aer.c | 35 ++++++++++++++++++++++++++---------
drivers/pci/pcie/rcec.c | 14 ++++++++++++++
3 files changed, 46 insertions(+), 10 deletions(-)
--
2.53.0
next reply other threads:[~2026-11-03 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 9:45 Lukas Wunner [this message]
2026-11-03 9:45 ` [PATCH 1/2] PCI/AER: Avoid NULL pointer deref on search for Error Source Lukas Wunner
2026-11-03 9:56 ` sashiko-bot
2026-11-03 12:39 ` Ilpo Järvinen
2026-11-03 16:08 ` Kuppuswamy Sathyanarayanan
2026-11-03 9:45 ` [PATCH 2/2] PCI/AER: Check validity of Error Source ID register Lukas Wunner
2026-11-03 10:11 ` sashiko-bot
2026-11-03 17:29 ` Lukas Wunner
2026-11-03 12:57 ` Ilpo Järvinen
2026-11-04 0:46 ` Bjorn Helgaas
2026-11-04 1:06 ` Ilpo Järvinen
2026-11-03 16:15 ` 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=cover.1793697480.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=Maciej.Grochowski@sony.com \
--cc=alexander.deucher@amd.com \
--cc=helgaas@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@gmail.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=sourabhjain@linux.ibm.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