From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: linux-pci@vger.kernel.org, "Bjorn Helgaas" <bhelgaas@google.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Kai-Heng Feng" <kaihengf@nvidia.com>,
"Rob Herring" <robh@kernel.org>,
linux-kernel@vger.kernel.org,
"Krzysztof Wilczyński" <kw@linux.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 2/3] PCI: Do not coalesce host bridge resource structs in place
Date: Wed, 15 Oct 2025 17:29:09 +0300 [thread overview]
Message-ID: <aO-vtdECWNpYpo6f@smile.fi.intel.com> (raw)
In-Reply-To: <20251010144231.15773-3-ilpo.jarvinen@linux.intel.com>
On Fri, Oct 10, 2025 at 05:42:30PM +0300, Ilpo Järvinen wrote:
> The resource coalescing for host bridge windows in
> pci_register_host_bridge() can alter the underlying struct resource
> which is inherently dangerous as this code has no knowledge of who else
> holds a pointer the same resource.
>
> Merge the struct resource inside a newly added
> resource_list_merge_entries() which uses the internal __res member of
> the struct resource_entry to store the merged resource, thus preserving
> the original resource structs.
...
> +static void resource_clear_tree_links(struct resource *res)
> +{
> + res->parent = NULL;
> + res->child = NULL;
> + res->sibling = NULL;
> +}
Not sure if this is the best location to inject a new helper to in the code
(I mean the position in the file). But I leave it to you just to give another
look in case something more suitable can be found.
> static int __release_resource(struct resource *old, bool release_child)
...
> +/**
> + * resource_mergeable - Test if resources are contiguous and can be merged
> + * @r1: first resource
> + * @r2: second resource
> + *
> + * Tests @r1 is followed by @r2 contiguously and share the metadata.
This needs an additional explanation about name equivalence that's not only by
pointers, but by a content.
> + * Return: %true if resources are mergeable non-destructively.
> + */
> +static bool resource_mergeable(struct resource *r1, struct resource *r2)
> +{
> + if ((r1->flags != r2->flags) ||
> + (r1->desc != r2->desc) ||
> + (r1->parent != r2->parent) ||
> + (r1->end + 1 != r2->start))
> + return false;
> + if (r1->name == r2->name)
> + return true;
> +
> + if (r1->name && r2->name && !strcmp(r1->name, r2->name))
> + return true;
> +
> + return false;
Hmm... Can we keep the logic more straight as in returning false cases as soon
as possible?
I think of something like this:
if (r1->name && r2->name)
return strcmp(r1->name, r2->name) == 0;
return r1->name == r2->name;
> +}
...
> + new_res->start = res->start;
> + new_res->end = next_res->end;
> + new_res->name = res->name;
> + new_res->flags = res->flags;
> + new_res->desc = res->desc;
Hmm... IIRC I saw similar code lines a few times in the kernel in resource.c
and might be elsewhere. Perhaps a time for another helper?
...
> + /* prepare for step 2), find res & next_res from child/sibling chain. */
> + p = &parent->child;
> + while (1) {
> + tmp = *p;
> + if (tmp == res)
> + break;
> +
> + /* No res in child/sibling, the resource tree is corrupted! */
Extra space which is not needed.
> + if (WARN_ON_ONCE(!tmp))
> + return -EINVAL;
> +
> + p = &tmp->sibling;
> + }
...
> static bool system_ram_resources_mergeable(struct resource *r1,
> struct resource *r2)
> {
> /* We assume either r1 or r2 is IORESOURCE_SYSRAM_MERGEABLE. */
> - return r1->flags == r2->flags && r1->end + 1 == r2->start &&
> - r1->name == r2->name && r1->desc == r2->desc &&
> + return resource_mergeable(r1, r2) &&
> !r1->child && !r2->child;
Now one line?
> }
> +struct resource_entry *resource_list_merge_entries(struct resource_entry *entry,
> + struct resource_entry *next)
> +{
> + struct resource *res = entry->res, *next_res = next->res, *new_res;
> + int ret;
> +
> + if ((entry->offset != next->offset) ||
> + !resource_mergeable(res, next_res))
One line? (It's only 82 characters long)
> + return ERR_PTR(-EINVAL);
> +
> + /* Use the internal __res to not mutate the input resources. */
> + struct resource_entry __free(kfree) *new = resource_list_create_entry(NULL, 0);
> + if (!new)
> + return ERR_PTR(-ENOMEM);
> +
> + new->offset = next->offset;
> + new_res = new->res;
> +
> + ret = resource_coalesce(res, next_res, new_res);
> + if (ret)
> + return ERR_PTR(ret);
> +
> + resource_list_add_tail(new, &entry->node);
> + resource_list_destroy_entry(entry);
> + resource_list_destroy_entry(next);
> +
> + return no_free_ptr(new);
> +}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-10-18 17:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 14:42 [PATCH 0/3] PCI & resource: Make coalescing host bridge windows safer Ilpo Järvinen
2025-10-10 14:42 ` [PATCH 1/3] PCI: Refactor host bridge window coalescing loop to use prev Ilpo Järvinen
2025-10-10 14:42 ` [PATCH 2/3] PCI: Do not coalesce host bridge resource structs in place Ilpo Järvinen
2025-10-15 14:29 ` Andy Shevchenko [this message]
2025-10-20 17:21 ` Ilpo Järvinen
2025-10-20 17:44 ` Andy Shevchenko
2025-10-20 18:15 ` Ilpo Järvinen
2025-10-20 18:30 ` Andy Shevchenko
2025-10-10 14:42 ` [PATCH 3/3] resource, kunit: add test case for resource_coalesce() Ilpo Järvinen
2025-10-20 13:42 ` [PATCH 0/3] PCI & resource: Make coalescing host bridge windows safer Geert Uytterhoeven
2025-10-20 16:20 ` Ilpo Järvinen
2025-10-21 7:44 ` Geert Uytterhoeven
2025-10-21 11:54 ` Ilpo Järvinen
2025-10-21 15:49 ` Andy Shevchenko
2025-10-21 16:09 ` Ilpo Järvinen
2025-10-22 7:19 ` Geert Uytterhoeven
2025-10-22 7:45 ` Geert Uytterhoeven
2025-10-22 11:13 ` Ilpo Järvinen
2025-10-22 12:14 ` Ilpo Järvinen
2025-10-22 12:51 ` Rob Herring
2025-10-23 23:02 ` Bjorn Helgaas
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=aO-vtdECWNpYpo6f@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=geert@linux-m68k.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kaihengf@nvidia.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh@kernel.org \
/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