public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Keith Busch <kbusch@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: Mon, 27 Apr 2026 17:28:52 -0500	[thread overview]
Message-ID: <20260427222852.GA199990@bhelgaas> (raw)
In-Reply-To: <aevqGci1hLqZQdOF@kbusch-mbp>

On Fri, Apr 24, 2026 at 04:09:29PM -0600, Keith Busch wrote:
> 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.

Thanks for the heads-up; I moved this to pci/for-linus for v7.1.

      reply	other threads:[~2026-04-27 22:28 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
2026-04-27 22:28     ` Bjorn Helgaas [this message]

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=20260427222852.GA199990@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=kbusch@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