Re: [PATCH 06/16] irqchip/loongson-liointc: unmap per-core iomaps on error

On Tue, 2026-07-14 at 21:24 +0800, Haofeng Li wrote:
> From: Haofeng Li <[email protected]>
>=20
> For revision > 1, liointc_init() maps per-core ISR regions with
> of_iomap(). out_iounmap only unmapped the main base, leaking successful
> per-core mappings on later failures.
>=20
> On the error path, iounmap any core_isr entry that is not an offset into
> the main base mapping.
>=20
> Fixes: 0858ed035a85 ("irqchip/loongson-liointc: Add ACPI init support")
> Signed-off-by: Haofeng Li <[email protected]>
> ---
> =C2=A0drivers/irqchip/irq-loongson-liointc.c | 8 ++++++++
> =C2=A01 file changed, 8 insertions(+)
>=20
> diff --git a/drivers/irqchip/irq-loongson-liointc.c b/drivers/irqchip/irq=
-loongson-liointc.c
> index cf44a333b9c8..6451d8b466ce 100644
> --- a/drivers/irqchip/irq-loongson-liointc.c
> +++ b/drivers/irqchip/irq-loongson-liointc.c
> @@ -312,6 +312,14 @@ static int liointc_init(phys_addr_t addr, unsigned l=
ong size, int revision,
> =C2=A0out_free_domain:
> =C2=A0	irq_domain_remove(domain);
> =C2=A0out_iounmap:
> +	if (revision > 1) {
> +		for (i =3D 0; i < LIOINTC_NUM_CORES; i++) {
> +			void __iomem *core_base =3D base + LIOINTC_REG_INTC_STATUS(i);
> +
> +			if (priv->core_isr[i] && priv->core_isr[i] !=3D core_base)

The first condition here is unnecessary. It's safe to call iounmap()
with a NULL pointer (like most deallocation functions in Linux).

Can you please explain why the second condition is needed? Even if the
physical ranges happen to overlap, they are mapped independently via
the of_iomap() call earlier in the function. That allocates a separate
vm area (and a PTE) that still needs to be freed.

FWIW, in the two relevant device trees I could find, the physical
ranges do *not* overlap:
arch/loongarch/boot/dts/loongson-2k0500.dtsi
arch/loongarch/boot/dts/loongson-2k1000.dtsi

> +				iounmap(priv->core_isr[i]);
> +		}
> +	}
> =C2=A0	iounmap(base);
> =C2=A0out_free_priv:
> =C2=A0	kfree(priv);