Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 16 Jan 2023 14:55:05 +0100
From:   Johan Hovold <johan@kernel.org>
To:     Mark-PK Tsai <mark-pk.tsai@mediatek.com>
Cc:     johan+linaro@kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
        maz@kernel.org, platform-driver-x86@vger.kernel.org,
        tglx@linutronix.de, x86@kernel.org, yj.chiang@mediatek.com,
        phil.chang@mediatek.com
Subject: Re: [PATCH v3 0/19] irqdomain: fix mapping race and clean up locking
Message-ID: <Y8VXOQy09lJ+obLE@hovoldconsulting.com>
References: <20221209140150.1453-1-johan+linaro@kernel.org>
 <20221220033042.27724-1-mark-pk.tsai@mediatek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221220033042.27724-1-mark-pk.tsai@mediatek.com>
Precedence: bulk

On Tue, Dec 20, 2022 at 11:30:42AM +0800, Mark-PK Tsai 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.

> Tested-by: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
> 
> We have the same issue and this patch series fix that.
> Thanks!
> 
> Link: https://lore.kernel.org/lkml/20221219130620.21092-1-mark-pk.tsai@mediatek.com/

Thanks for confirming. I just sent a v4 with a couple of clarifying
comments added to the final patch.

Johan