From: sashiko-bot@kernel.org
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: wsa+renesas@sang-engineering.com, robh@kernel.org,
linux-pci@vger.kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v5 3/4] PCI: rzg3s-host: Prepare System Controller handling for multiple controllers
Date: Mon, 29 Jun 2026 22:21:13 +0000 [thread overview]
Message-ID: <20260629222113.920291F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260629220932.861445-4-prabhakar.mahadev-lad.rj@bp.renesas.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Failure to clear chained IRQ handlers in the error path leads to a Use-After-Free of the `host` structure.
--
commit 9d15bfaf7ab0514922ec90d6892801c1f1eeb157
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
PCI: rzg3s-host: Prepare System Controller handling for multiple controllers
This commit prepares the RZ/G3S PCIe driver to support multiple PCIe
controllers by extending the System Controller (SYSC) information storage.
It introduces an array of sysc_info structures indexed by a new controller
ID field. Existing single-controller SoCs remain functionally unchanged.
> diff --git a/drivers/pci/controller/pcie-rzg3s-host.c b/drivers/pci/controller/pcie-rzg3s-host.c
> index cca2617f29157..03d79e98c9c99 100644
> --- a/drivers/pci/controller/pcie-rzg3s-host.c
> +++ b/drivers/pci/controller/pcie-rzg3s-host.c
[ ... ]
> @@ -1699,7 +1713,7 @@ static int rzg3s_pcie_probe(struct platform_device *pdev)
> return -ENOMEM;
>
> sysc = host->sysc;
> - sysc->info = &host->data->sysc_info;
> + sysc->info = &host->data->sysc_info[host->controller_id];
[Severity: High]
This is a pre-existing issue, but I noticed a potential memory safety concern
in the error handling path of rzg3s_pcie_probe().
If probe fails later and executes the error path, it calls
rzg3s_pcie_teardown_irqdomain(). Looking at rzg3s_pcie_teardown_irqdomain(),
it executes:
irq_domain_remove(host->intx_domain);
However, it does not appear to clear the chained interrupt handlers.
Because the host structure is allocated via devm_pci_alloc_host_bridge(),
it will be automatically freed when the probe fails.
Could this leave a dangling pointer in the parent interrupt controller,
resulting in a use-after-free if the hardware triggers
rzg3s_pcie_intx_irq_handler() after the teardown?
>
> host->axi = devm_platform_ioremap_resource(pdev, 0);
> if (IS_ERR(host->axi))
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260629220932.861445-1-prabhakar.mahadev-lad.rj@bp.renesas.com?part=3
next prev parent reply other threads:[~2026-06-29 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 22:09 [PATCH v5 0/4] Add PCIe support for RZ/V2H(P) SoC Prabhakar
2026-06-29 22:09 ` [PATCH v5 1/4] dt-bindings: PCI: renesas,r9a08g045-pcie: Add RZ/V2H(P) support Prabhakar
2026-06-29 22:15 ` sashiko-bot
2026-06-29 22:09 ` [PATCH v5 2/4] PCI: rzg3s-host: Use shared reset controls for power domain resets Prabhakar
2026-06-29 22:19 ` sashiko-bot
2026-06-29 22:09 ` [PATCH v5 3/4] PCI: rzg3s-host: Prepare System Controller handling for multiple controllers Prabhakar
2026-06-29 22:21 ` sashiko-bot [this message]
2026-06-29 22:09 ` [PATCH v5 4/4] PCI: rzg3s-host: Add support for RZ/V2H(P) SoC Prabhakar
2026-06-29 22:16 ` sashiko-bot
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=20260629222113.920291F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.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