From: sashiko-bot@kernel.org
To: "Anthony Pighin" <anthony.pighin@nokia.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Don't report fully optional resources as assignment failures
Date: Fri, 17 Jul 2026 18:13:12 +0000 [thread overview]
Message-ID: <20260717181312.D8D861F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260717180029.1829888-1-anthony.pighin@nokia.com>
> A hotplug bridge may request a window with required size 0 plus
> add_size headroom. For example, the PCI core speculatively requests
> a non-prefetchable MMIO reserve for a hotplug bridge even when no
> downstream BAR currently requires that space.
>
> reassign_resources_sorted() temporarily grows an unassigned resource
> from its required size to the required size plus add_size. If
> pci_assign_resource() fails, the failure is ignored because the
> additional space is optional, but the resource is left unassigned at
> the enlarged size.
>
> Since commit 96336ec70264 ("PCI: Perform reset_resource() and build
> fail list in sync") and commit 2499f5348431 ("PCI: Rework optional
> resource handling"), the __assign_resources_sorted() out path
> unconditionally adds every remaining unassigned resource to fail_head.
> [ ... ]
>
> Fixes: 96336ec70264 ("PCI: Perform reset_resource() and build fail list in sync")
> Fixes: 2499f5348431 ("PCI: Rework optional resource handling")
> Cc: stable@vger.kernel.org
> Signed-off-by: Anthony Pighin <anthony.pighin@nokia.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260717180029.1829888-1-anthony.pighin@nokia.com?part=1
next prev parent reply other threads:[~2026-07-17 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 18:00 [PATCH] PCI: Don't report fully optional resources as assignment failures Anthony Pighin
2026-07-17 18:13 ` sashiko-bot [this message]
2026-07-20 13:21 ` Ilpo Järvinen
2026-07-27 19:39 ` Anthony Pighin
2026-07-28 10:56 ` Ilpo Järvinen
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=20260717181312.D8D861F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=anthony.pighin@nokia.com \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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