The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Guenter Roeck" <linux@roeck-us.net>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Michał Winiarski" <michal.winiarski@intel.com>
Subject: Re: [PATCH 1/1] PCI: Restore assigned resources fully after release
Date: Fri, 18 Apr 2025 17:41:13 +0300 (EEST)	[thread overview]
Message-ID: <f3e94bb7-ae6a-724a-107a-29889acc3642@linux.intel.com> (raw)
In-Reply-To: <20250417163904.GA114476@bhelgaas>

[-- Attachment #1: Type: text/plain, Size: 2712 bytes --]

On Thu, 17 Apr 2025, Bjorn Helgaas wrote:

> On Thu, Apr 03, 2025 at 12:31:37PM +0300, Ilpo Järvinen wrote:
> > PCI resource fitting code in __assign_resources_sorted() runs in
> > multiple steps. A resource that was successfully assigned may have to
> > be released before the next step attempts assignment again. The
> > assign+release cycle is destructive to a start-aligned struct resource
> > (bridge window or IOV resource) because the start field is overwritten
> > with the real address when the resource got assigned.
> > 
> > Properly restore the resource after releasing it. The start, end, and
> > flags fields must be stored into the related struct pci_dev_resource in
> > order to be able to restore the resource to its original state.
> > 
> > Reported-by: Guenter Roeck <linux@roeck-us.net>
> > Fixes: 96336ec70264 ("PCI: Perform reset_resource() and build fail list in sync")
> > Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> 
> Applied to pci/for-linus for v6.15, thanks!
> 
> I'd like to add the following to the commit log if it's accurate:
> 
>   + One symptom:
> 
>   +   pci 0002:00:00.0: bridge window [mem size 0x00100000]: can't assign; bogus alignment

Yes, that is a good addition.

-- 
 i.

>     Reported-by: Guenter Roeck <linux@roeck-us.net>
>   + Closes: https://lore.kernel.org/r/01eb7d40-f5b5-4ec5-b390-a5c042c30aff@roeck-us.net/
>   + Reported-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
>   + Closes: https://lore.kernel.org/r/3578030.5fSG56mABF@workhorse
> 
> Let me know if that's wrong or there are additional reports.
> 
> > ---
> >  drivers/pci/setup-bus.c | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/drivers/pci/setup-bus.c b/drivers/pci/setup-bus.c
> > index 54d6f4fa3ce1..e994c546422c 100644
> > --- a/drivers/pci/setup-bus.c
> > +++ b/drivers/pci/setup-bus.c
> > @@ -187,6 +187,9 @@ static void pdev_sort_resources(struct pci_dev *dev, struct list_head *head)
> >  			panic("%s: kzalloc() failed!\n", __func__);
> >  		tmp->res = r;
> >  		tmp->dev = dev;
> > +		tmp->start = r->start;
> > +		tmp->end = r->end;
> > +		tmp->flags = r->flags;
> >  
> >  		/* Fallback is smallest one or list is empty */
> >  		n = head;
> > @@ -545,6 +548,7 @@ static void __assign_resources_sorted(struct list_head *head,
> >  		pci_dbg(dev, "%s %pR: releasing\n", res_name, res);
> >  
> >  		release_resource(res);
> > +		restore_dev_resource(dev_res);
> >  	}
> >  	/* Restore start/end/flags from saved list */
> >  	list_for_each_entry(save_res, &save_head, list)
> > 
> > base-commit: 7d06015d936c861160803e020f68f413b5c3cd9d
> > -- 
> > 2.39.5
> > 
> 

      reply	other threads:[~2025-04-18 14:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03  9:31 [PATCH 1/1] PCI: Restore assigned resources fully after release Ilpo Järvinen
2025-04-03 12:16 ` Guenter Roeck
2025-04-14 13:29 ` Ondřej Jirman
2025-04-17 14:49 ` Nicolas Frattaroli
2025-04-17 16:39 ` Bjorn Helgaas
2025-04-18 14:41   ` Ilpo Järvinen [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=f3e94bb7-ae6a-724a-107a-29889acc3642@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=imammedo@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=michal.winiarski@intel.com \
    --cc=mika.westerberg@linux.intel.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