public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Shawn Jin <shawn.jin@asteralabs.com>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [BUG] PCIe bridge resource allocation creates invalid limit addresses after Secondary Bus Reset recovery
Date: Thu, 12 Mar 2026 12:34:30 -0500	[thread overview]
Message-ID: <20260312173430.GA1108119@bhelgaas> (raw)
In-Reply-To: <LV8P221MB147241DCED82480888F8D73D9947A@LV8P221MB1472.NAMP221.PROD.OUTLOOK.COM>

On Thu, Mar 12, 2026 at 12:02:14AM +0000, Shawn Jin wrote:
> On Wed, Mar 11, 2026 at 10:00:39PM +0000, Shawn Jin wrote:
> > I'm reporting a potential critical bug in the Linux kernel's PCIe
> > resource allocation code that creates invalid bridge window limit
> > addresses during hotplug re-enumeration after Secondary Bus Reset
> > (SBR) recovery.
> 
> Thanks for the report and the repro and debugging information!
> 
> > ## AFFECTED KERNEL VERSIONS
> > - Confirmed: 5.15.0, 6.8.0 (Ubuntu 6.8.0-88-generic, 6.8.0-90-generic)
> > - Likely affected: All recent kernels including 6.19
> 
> Do you know of any kernels that are *not* affected?  If you do, we
> could bisect.
> 
> <SJ> I haven't tried the latest kernel 6.19 yet. I'm planning to
> install the openSUSE Tumbleweed with kernel 6.19.

I didn't notice at first, but AFAICS the most recent kernel you've
actually tested is v6.8, and "6.19 likely affected" is just
speculation.

There have been a lot of resource assignment changes since then, so
I doubt it's worth testing/debugging these old kernels until we
actually know the problem happens on v6.19 or v7.0-rc1.

IMO we should start by debugging the current kernel, fix the issue
there, then decide about backporting.

Bjorn

  parent reply	other threads:[~2026-03-12 17:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11 22:00 [BUG] PCIe bridge resource allocation creates invalid limit addresses after Secondary Bus Reset recovery Shawn Jin
2026-03-11 23:19 ` Bjorn Helgaas
2026-03-12  0:02   ` Shawn Jin
2026-03-12  1:03     ` Shawn Jin
2026-03-12 13:24       ` Ilpo Järvinen
2026-03-12 17:14         ` Shawn Jin
2026-03-12 17:48           ` Ilpo Järvinen
2026-03-13 16:48             ` Shawn Jin
2026-03-16 10:28               ` Ilpo Järvinen
2026-03-16 17:26                 ` Shawn Jin
2026-03-12 17:34     ` Bjorn Helgaas [this message]
2026-03-12 17:40       ` Shawn Jin

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=20260312173430.GA1108119@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=shawn.jin@asteralabs.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