[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o7scd197.ffs@tglx>
Date: Fri, 09 Dec 2022 16:51:00 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Johan Hovold <johan+linaro@...nel.org>,
Marc Zyngier <maz@...nel.org>
Cc: x86@...nel.org, platform-driver-x86@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org,
Johan Hovold <johan+linaro@...nel.org>
Subject: Re: [PATCH v3 00/19] irqdomain: fix mapping race and clean up locking
Johan!
On Fri, Dec 09 2022 at 15:01, Johan Hovold wrote:
> Parallel probing (e.g. due to asynchronous probing) of devices that
> share interrupts can currently result in two mappings for the same
> hardware interrupt to be created.
>
> This series fixes this mapping race and clean up the irqdomain locking
> so that in the end the global irq_domain_mutex is only used for managing
> the likewise global irq_domain_list, while domain operations (e.g.
> IRQ allocations) use per-domain (hierarchy) locking.
Can you please rebase that on top of:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/core
Thanks,
tglx
Powered by blists - more mailing lists