diff options
| author | Fuad Tabba <fuad.tabba@linux.dev> | 2026-09-25 09:50:00 +0100 |
|---|---|---|
| committer | Thomas Gleixner <tglx@kernel.org> | 2026-10-15 11:55:41 +0200 |
| commit | 6a21693b97ee5cb0a21d04bfd051a05dde5aa783 (patch) | |
| tree | fa51241a2f3a4909449da0eee9a179091dc20714 /scripts/Makefile.thinlto | |
| parent | d09b36d8e0e60f35bd1cd7d63aadc6dfad61700c (diff) | |
| download | linux-6a21693b97ee5cb0a21d04bfd051a05dde5aa783.tar.gz linux-6a21693b97ee5cb0a21d04bfd051a05dde5aa783.zip | |
irqchip/gic-v3: Don't register a redistributor that was never counted
gic_acpi_match_gicc() counts only the enabled GICCs with a non-zero
gicr_base_address, and that count sizes redist_regs[], but
gic_acpi_parse_madt_gicc() registers every enabled one. On a MADT with
no GICR entries, an enabled GICC with a zero GICR base therefore makes
gic_acpi_register_redist() write a struct redist_region past the end of
the array.
Commit fa2dabe57220e ("irqchip/gic-v3: Don't return errors from
gic_acpi_match_gicc()") removed the check that kept the two consistent.
Its message says such entries are still caught by gic_populate_rdist(),
but that runs from gic_cpu_init(), after the write.
Skip the entry instead, and mark the CPU's redistributor broken as the
online-capable path does, so that gic_check_rdist() rejects the CPU.
gic_starting_cpu() runs past cpuhp's last failure point, so without the
mark the CPU would come online with its redistributor and CPU interface
unconfigured. With an ITS, its_cpu_init() would then dereference a NULL
rd_base.
Fixes: fa2dabe57220e ("irqchip/gic-v3: Don't return errors from gic_acpi_match_gicc()")
Signed-off-by: Fuad Tabba <fuad.tabba@linux.dev>
Signed-off-by: Thomas Gleixner <tglx@kernel.org>
Reviewed-by: Marc Zyngier <maz@kernel.org>
Link: https://patch.msgid.link/20260925085000.753400-4-fuad.tabba@linux.dev
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
