Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 1/8] resource: Mark free space assigned
Date: Tue, 13 Oct 2026 13:28:05 +0000	[thread overview]
Message-ID: <sashiko-outbox-169814@kernel.org> (raw)
In-Reply-To: <20261013130948.6231-2-ilpo.jarvinen@linux.intel.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] resource: incomplete fix for %pR format on candidate resource
--

commit 094e97a90a5417acb103a184b0b1c36691f9e6c3
Author: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>

resource: Mark free space assigned

This commit clears the IORESOURCE_UNSET flag from the free space indicator
resource (full_avail). This prevents the flag from hampering the printing
of the resource with the %pR format specifier.

> diff --git a/kernel/resource.c b/kernel/resource.c
> index e60539a55541d..17e7fccd859cb 100644
> --- a/kernel/resource.c
> +++ b/kernel/resource.c
> @@ -731,6 +731,7 @@ static int __find_resource_space(struct resource *root, struct resource *old,
>  	resource_alignf alignf = constraint->alignf;
>  
>  	full_avail.start = root->start;
> +	full_avail.flags &= ~IORESOURCE_UNSET;

[Severity: Low]
Is this fix incomplete?

Later in __find_resource_space(), the candidate resource 'avail' inherits
flags from the unassigned resource 'new':

kernel/resource.c:__find_resource_space() {
    ...
		/* Check for overflow after ALIGN() */
		avail.start = ALIGN(full_avail.start, constraint->align);
		avail.end = full_avail.end;
		avail.flags = new->flags;
    ...
}

Because 'new->flags' still has IORESOURCE_UNSET set, 'avail' inherits it.
When 'avail' is passed to alignf callbacks (such as pcibios_align_resource
in arch/parisc/kernel/pci.c), any %pR debug prints of this candidate
resource will incorrectly format it as a size rather than revealing the
candidate address range.

Does IORESOURCE_UNSET need to be cleared for 'avail.flags' as well to
fully resolve this %pR formatting issue?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261013130948.6231-1-ilpo.jarvinen@linux.intel.com?part=1

  reply	other threads:[~2026-10-13 13:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 13:09 [PATCH v3 0/8] PCI: Resource placement algorithm fixes Ilpo Järvinen
2026-10-13 13:09 ` [PATCH v3 1/8] resource: Mark free space assigned Ilpo Järvinen
2026-10-13 13:28   ` sashiko-bot [this message]
2026-10-13 13:09 ` [PATCH v3 2/8] PCI/parisc: Clean up resource debug print & use dynamic debug Ilpo Järvinen
2026-10-13 13:19   ` sashiko-bot
2026-10-13 13:09 ` [PATCH v3 3/8] PCI: Honor alignment overrides Ilpo Järvinen
2026-10-13 13:24   ` sashiko-bot
2026-10-13 14:08   ` Rodrigo Vivi
2026-10-13 13:09 ` [PATCH v3 4/8] PCI: Fix nesting windows with remainder at the left edge Ilpo Järvinen
2026-10-13 13:25   ` sashiko-bot
2026-10-13 13:09 ` [PATCH v3 5/8] linux/log2.h: Add 64-bit roundup/down_pow_of_two64() variants Ilpo Järvinen
2026-10-13 13:16   ` sashiko-bot
2026-10-13 13:09 ` [PATCH v3 6/8] PCI: Place resources to either edge of the window Ilpo Järvinen
2026-10-13 13:19   ` sashiko-bot
2026-10-13 13:09 ` [PATCH v3 7/8] PCI: Fix composite resource sizing Ilpo Järvinen
2026-10-13 13:26   ` sashiko-bot
2026-10-13 13:09 ` [PATCH v3 8/8] PCI/quirks: Avoid certain address on Genoa systems Ilpo Järvinen
2026-10-13 13:24   ` sashiko-bot
2026-10-13 17:00   ` Mario Limonciello
2026-10-13 17:03     ` Mario Limonciello
2026-10-13 17:26       ` Ilpo Järvinen
2026-10-13 18:59         ` Mario Limonciello

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=sashiko-outbox-169814@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.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