[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y2jl81ft.fsf@nanos.tec.linutronix.de>
Date: Sun, 01 Nov 2020 17:52:06 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Marc Zyngier <maz@...nel.org>, 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 Sun, Nov 01 2020 at 12:10, Marc Zyngier wrote:
> 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!
That should go into urgent, the offending commit is in Linus tree already
Thanks,
tglx
Powered by blists - more mailing lists