[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <160423261831.76459.6853837344029171039.b4-ty@kernel.org>
Date: Sun, 1 Nov 2020 12:10:27 +0000
From: Marc Zyngier <maz@...nel.org>
To: Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Greentime Hu <greentime.hu@...ive.com>, palmer@...belt.com,
linux-kernel@...r.kernel.org, atish.patra@....com,
linux-riscv@...ts.infradead.org, paul.walmsley@...ive.com,
anup@...infault.org
Cc: Ulrich Hecht <uli+renesas@...nd.eu>,
linux-renesas-soc@...r.kernel.org
Subject: Re: [RFC PATCH] irqchip/sifive-plic: Fix getting wrong chip_data when interrupt is hierarchy
On Thu, 29 Oct 2020 10:37:38 +0800, Greentime Hu wrote:
> This oops is caused by a wrong chip_data and it is because plic_irq_unmask
> uses irq_get_chip_data(irq_data->irq) to get the chip_data. However it may
> get another irq_data with the same irq_data->irq if it is hierarchy.
>
> In this case, it will get irq_data of sifive_gpio_irqchip instead of
> plic_chip so that it will get a wrong chip_data and then the wrong lmask
> of it to cause this oops.
>
> [...]
Applied to irq/irqchip-next, thanks!
[1/1] irqchip/sifive-plic: Fix chip_data access within a hierarchy
commit: f9ac7bbd6e4540dcc6df621b9c9b6eb2e26ded1d
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists