From: Aditya Gupta <adityag@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Timothy Pearson <tpearson@raptorengineering.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Shawn Anastasio <sanastasio@raptorengineering.com>
Cc: sashiko-bot@kernel.org, linux-pci@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Subject: [PATCH v2 0/3] ppc/pnv: Fix panics and refactor pnv_php.c
Date: Wed, 27 May 2026 23:38:13 +0530 [thread overview]
Message-ID: <20260527180816.2749186-1-adityag@linux.ibm.com> (raw)
Overview
========
Since below upstream commit, powernv systems get a panic during boot when an
OpenCAPI hotplug slot is detected:
commit 80f9fc2362797538ebd4fd70a1dfa838cc2c2cdb
Date: Tue Jul 15 16:36:55 2025 -0500
PCI: pnv_php: Work around switches with broken presence detection
The panic log is present in patch #1
Patch #1: Adds null checks around null pointer dereferences
Patch #2: Rework the driver code to separate PCIe-specific and common code
Patch #3 (optional): Group PCIe functionality together, only code movements
Note: Patch 1 is important and independent of the other patches
Note2: Patch 2 & 3 can be squashed into 1 commit. Intentionally kept patch #2 as
small as possible for ease of review.
Changelog
=========
v1 -> v2:
* Sashiko pointed out various null pointer dereferences including a kernel panic triggered by userspace, fixed them
* Add rework patches, so that PCIe-specific and common code can be separated
cleanly
Aditya Gupta (3):
ppc/pnv: Add null checks for OpenCapi PHBs
ppc/pnv: Refactor PNV PCI hotplug driver
ppc/pnv: Refactor PNV PCI Hotplug to group PCIe functions
arch/powerpc/include/asm/pnv-pci.h | 16 +
drivers/pci/hotplug/pnv_php.c | 554 ++++++++++++++++-------------
2 files changed, 328 insertions(+), 242 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-27 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 18:08 Aditya Gupta [this message]
2026-05-27 18:08 ` [PATCH v2 1/3] ppc/pnv: Add null checks for OpenCapi PHBs Aditya Gupta
2026-06-08 15:39 ` Bjorn Helgaas
2026-06-09 8:51 ` Aditya Gupta
2026-05-27 18:08 ` [PATCH v2 2/3] ppc/pnv: Refactor PNV PCI hotplug driver Aditya Gupta
2026-05-27 18:08 ` [PATCH v2 3/3] ppc/pnv: Refactor PNV PCI Hotplug to group PCIe functions Aditya Gupta
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=20260527180816.2749186-1-adityag@linux.ibm.com \
--to=adityag@linux.ibm.com \
--cc=bhelgaas@google.com \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=sanastasio@raptorengineering.com \
--cc=sashiko-bot@kernel.org \
--cc=tpearson@raptorengineering.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