Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Bjorn Helgaas" <helgaas@kernel.org>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH v3] PCI: of_property: Omit bus properties without a subordinate bus
Date: Fri, 18 Sep 2026 20:02:20 +0000	[thread overview]
Message-ID: <20260918200220.C4EC41F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918195540.GA1187209@bhelgaas>

> Author: Angel J <iamanaws@httpd.dev>
> 
> PCI: of_property: Omit bus properties without a subordinate bus
> 
> A bridge (a device with a Type 1 header) may not have a secondary bus
> allocated (pdev->subordinate), e.g., if there are no available bus numbers
> or the bridge secondary/subordinate bus numbers are not writable.
> 
> The dynamic OF helpers of_pci_prop_bus_range() and of_pci_prop_intr_map()
> dereference pdev->subordinate without checking it.  When
> CONFIG_PCI_DYNAMIC_OF_NODES is enabled, this can cause a NULL pointer
> dereference and early boot hang.
> 
> Generate 'bus-range' and 'interrupt-map' properties only when a subordinate
> bus exists.  Keep the node and its remaining properties for bridges without
> one.
> 
> The problem was latent since 407d1a51921e ("PCI: Create device tree node
> for bridge"), but wasn't reachable until 1f340724419e ("PCI: of: Create
> device tree PCI host bridge node"), which appeared in v6.15.  Before
> 1f340724419e, of_pci_make_dev_node() returned early because the parent OF
> node was missing.
> 
> Fixes: 407d1a51921e ("PCI: Create device tree node for bridge")
> Signed-off-by: Angel J <iamanaws@httpd.dev>
> [bhelgaas: move pdev->subordinate test to callees, commit log]
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260918195540.GA1187209@bhelgaas?part=1


  reply	other threads:[~2026-09-18 20:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23  2:14 [REGRESSION] PCI: Dynamic OF node creation hangs on invalid bridge configuration Angel J
2026-09-01  0:59 ` Angel J
2026-09-01  6:07   ` Thorsten Leemhuis
2026-09-03 23:17 ` Bjorn Helgaas
2026-09-04  8:57   ` Herve Codina
2026-09-09 11:27     ` Andrea della Porta
2026-09-11 23:01 ` Angel J
2026-09-11 23:04   ` [PATCH] PCI: of: Skip dynamic nodes for bridges without a subordinate bus Angel J
2026-09-11 23:13     ` sashiko-bot
2026-09-12  4:31     ` [PATCH v2] PCI: of_property: Omit bus properties " Angel J
2026-09-12  4:42       ` sashiko-bot
2026-09-16 14:50       ` Bjorn Helgaas
2026-09-18 19:55         ` [PATCH v3] " Bjorn Helgaas
2026-09-18 20:02           ` sashiko-bot [this message]
2026-09-18 20:20           ` Bjorn Helgaas
2026-09-18 20:24             ` Angel J
2026-09-14 11:53   ` [REGRESSION] PCI: Dynamic OF node creation hangs on invalid bridge configuration Andrea della Porta
2026-09-14 22:05     ` Angel J
2026-09-14 23:28       ` Angel J
2026-09-15 10:30         ` Andrea della Porta
2026-09-16  1:21         ` Bjorn Helgaas
2026-09-16 11:14           ` Angel J
2026-09-16 14:42             ` Bjorn Helgaas
2026-09-16 19:28             ` Sasha Levin

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=20260918200220.C4EC41F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=robh@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