From: Keith Busch <kbusch@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Keith Busch <kbusch@meta.com>,
linux-pci@vger.kernel.org, bhelgaas@google.com
Subject: Re: [PATCH] pci: don't fallback to bus reset after failed slot reset
Date: Fri, 24 Apr 2026 16:09:29 -0600 [thread overview]
Message-ID: <aevqGci1hLqZQdOF@kbusch-mbp> (raw)
In-Reply-To: <20260424161136.GA11831@bhelgaas>
On Fri, Apr 24, 2026 at 11:11:36AM -0500, Bjorn Helgaas wrote:
> On Tue, Apr 21, 2026 at 08:06:44AM -0700, Keith Busch wrote:
> > From: Keith Busch <kbusch@kernel.org>
> >
> > If a bus has hotplug slots that implement the slot's reset_slot
> > callback, it is not safe to do the non-slot specific bus reset, so don't
> > fallback to it. If a slot reset does fail, the subsequent bus reset will
> > attempt a 2nd link reset on top of previous and fail to handle the
> > hotplug events.
> >
> > Fixes: 8238cb69c01fe ("PCI: Make reset_subordinate hotplug safe")
> > Signed-off-by: Keith Busch <kbusch@kernel.org>
>
> Applied to pci/reset for v7.2, thanks! Will be rebased after
> v7.1-rc1.
I kind of think this is 7.1 material. If a pciehp slot reset fails
because of some hardware issue, that means the device is being removed
after disabling the hotplug "ignore". Falling back to a bus reset walks
the bus' device list without a lock, so it risks grabbing an invalid
pointer racing with the removal.
I didn't intend to get into those details because it may distract to the
pre-existing locking issues that you can hit from a variety of
directions. But for the record, the failure from this particular path
before this patch looks like this:
pcieport 0000:55:01.0: pciehp: Slot(30): Link Down/Up ignored
pcieport 0000:55:01.0: pciehp: Slot(30): Link Down
pcieport 0000:55:01.0: pciehp: Slot(30): Card not present
Oops: general protection fault, probably for non-canonical address 0xdead000000000180: 0000 [#1] SMP
...
RIP: 0010:pci_dev_save_and_disable+0x9/0x70
Code: 89 fe 48 89 c7 e8 57 9d 99 00 48 89 df e8 5f 5e ff ff 4c 89 f7 45 31 e4 e9 6c ff ff ff cc cc cc cc 0f 1f 44 00 00 53 48 89 fb <48> 8b 87 80 00 00 00 48 85 c0 75 27 48 89 df 31 f6 31 d2 e8 6f c1
RSP: 0018:ffa0000052f27db8 EFLAGS: 00010297
RAX: 0000000000000086 RBX: dead000000000100 RCX: 0000000000000000
RDX: 0000000000000400 RSI: 0000000000000004 RDI: dead000000000100
RBP: ff11000112c8f428 R08: 0000000000000002 R09: ffa0000052f27cfc
R10: ffffffff82b37718 R11: 0000000000000001 R12: ff11000112c8f440
R13: ff1100011024b508 R14: dead000000000100 R15: ff1100011024b500
FS: 00007f63b0ced740(0000) GS:ff11007eea90e000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f58fc1774e0 CR3: 00000003087c8002 CR4: 0000000000771ef0
PKRU: 55555554
Call Trace:
<TASK>
pci_bus_save_and_disable_locked+0x20/0x40
pci_reset_bridge+0x1e6/0x230
reset_subordinate_store+0x39/0x60
kernfs_fop_write_iter.llvm.2764860334700261357+0xd4/0x1d0
? do_timerfd_settime+0x490/0x490
__x64_sys_write+0x309/0x540
do_syscall_64+0x6b/0x250
entry_SYSCALL_64_after_hwframe+0x4b/0x53
next prev parent reply other threads:[~2026-04-24 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 15:06 [PATCH] pci: don't fallback to bus reset after failed slot reset Keith Busch
2026-04-24 16:11 ` Bjorn Helgaas
2026-04-24 22:09 ` Keith Busch [this message]
2026-04-27 22:28 ` Bjorn Helgaas
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=aevqGci1hLqZQdOF@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-pci@vger.kernel.org \
/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