[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251110225958.GA2142254@bhelgaas>
Date: Mon, 10 Nov 2025 16:59:58 -0600
From: Bjorn Helgaas <helgaas@...nel.org>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc: Alex Bennée <alex.bennee@...aro.org>,
Simon Richter <Simon.Richter@...yros.de>,
Lucas De Marchi <lucas.demarchi@...el.com>,
Alex Deucher <alexander.deucher@....com>,
amd-gfx@...ts.freedesktop.org, Bjorn Helgaas <bhelgaas@...gle.com>,
David Airlie <airlied@...il.com>, dri-devel@...ts.freedesktop.org,
intel-gfx@...ts.freedesktop.org, intel-xe@...ts.freedesktop.org,
Jani Nikula <jani.nikula@...ux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
linux-pci@...r.kernel.org, Rodrigo Vivi <rodrigo.vivi@...el.com>,
Simona Vetter <simona@...ll.ch>,
Tvrtko Ursulin <tursulin@...ulin.net>,
Christian König <christian.koenig@....com>,
Thomas Hellström <thomas.hellstrom@...ux.intel.com>,
Michał Winiarski <michal.winiarski@...el.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/9] PCI: Prevent resource tree corruption when BAR
resize fails
On Thu, Oct 30, 2025 at 10:22:27AM +0200, Ilpo Järvinen wrote:
> On Wed, 29 Oct 2025, Bjorn Helgaas wrote:
>
> > On Tue, Oct 28, 2025 at 07:35:43PM +0200, Ilpo Järvinen wrote:
> > > pbus_reassign_bridge_resources() saves bridge windows into the saved
> > > list before attempting to adjust resource assignments to perform a BAR
> > > resize operation. If resource adjustments cannot be completed fully,
> > > rollback is attempted by restoring the resource from the saved list.
> >
> > > Fixes: 8bb705e3e79d ("PCI: Add pci_resize_resource() for resizing BARs")
> > > Reported-by: Simon Richter <Simon.Richter@...yros.de>
> > > Reported-by: Alex Bennée <alex.bennee@...aro.org>
> >
> > If these reports were public, can we include lore URLs for them?
> >
> > Same question for [PATCH 5/9] PCI: Fix restoring BARs on BAR resize
> > rollback path.
> >
> > I put these all on pci/resource for build testing. I assume we'll
> > tweak these based on testing reports and sorting out the pci/rebar
> > conflicts.
>
> Thanks, the links will come in v2 along with fixing a few things found by
> more extensive tests by LKP. E.g., it seems clang thinks guard() cannot be
> used here because goto jumps over it (auto variable initialization gets
> skipped so it's kind of understandable limitation).
Just a ping on this. The lkp robot did build this fine:
https://lore.kernel.org/r/202510311139.1VIkw3Ez-lkp@intel.com
I'm happy to put it in pci/next as-is, especially if the amdgpu and
i915 folks are ok with it.
Powered by blists - more mailing lists