From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id DB168C982D7 for ; Sat, 19 Sep 2026 14:58:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:MIME-Version: Content-Transfer-Encoding:Content-Type:References:In-Reply-To:Date:Cc:To:From :Subject:Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=+TKok9hDY7p6Z7PJqFMlszfKsfnvblxalzrMKMB6/q0=; b=Das1b9o4gfP0Xy3vilao7Sbz/D NnzIh45npJMrUIr4g/Gwwjo5lhTbuxizxFclDIHFwIy+0uGUEwJk1M769359cuouCmk7VZ3X/cR5X /467UbAmCD5951UkVESkczQ7oryMCysiPKGNP/BEha97i+hYoMSk+K47bzSzvf0sEDa8tz7cpYuUr dZ+hWPW+MPIM4Lz3R/C6O9FC8QSABhwdmY+GkVA/jhH94G5xf8H1NIwz2b3BQ5ObBjIjWzMtgnGhp cXNvIg4/fon5ZN8dBQ2cUQyBsb4dv69ooFRM7K4oOAQqrqY4UBavjnv1GbmzlbvX4VuCIkDI/Swri ZepwN6Yg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1x7wWL-0000000GPO0-1Hn6; Sat, 19 Sep 2026 14:58:29 +0000 Received: from xs1.mindbit.ro ([80.86.107.70] helo=mail.mindbit.ro) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1x7wWI-0000000GPNV-34cO for linux-arm-kernel@lists.infradead.org; Sat, 19 Sep 2026 14:58:28 +0000 Received: from dog.kanata.rendec.net (pool-174-112-193-187.cpe.net.cable.rogers.com [174.112.193.187]) by mail.mindbit.ro (Postfix) with ESMTPSA id 76994D07A0; Sat, 19 Sep 2026 17:58:18 +0300 (EEST) DKIM-Filter: OpenDKIM Filter v2.11.0 mail.mindbit.ro 76994D07A0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rendec.net; s=default; t=1789829899; bh=+TKok9hDY7p6Z7PJqFMlszfKsfnvblxalzrMKMB6/q0=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=Jvp0Ar6xR4ZpiyfqrF7J0StzxmS2aizkdXj11lYVxsiDzhlswXGVjC3fU5+HrQrJs 15fJ9Cu8X59KIAoVI2VX9iMCPysTxorrPjnhvZqPcYj/LF5UuDPxuMobkHEBEa9yMQ AP5UvQ5VxX2wkwHPbIM8DWUq1HC/NOthnlrqzhv0YRTmgPwbRT8bGAVklmytEGMI3S t1tuJqNbA2fc+a1SBTKQrk5SLFI7C0j+7PsNqVvuBUGhUj0SVNX1Jy2acdcxUpcuMQ aGLy3GR/OpUrP1Oue+MKG6BElK1xSdY+R3PXfruUSOGfrPXAOaLlwjERnRKEE+Pvls tCkR0K6f9RHpg== Message-ID: <7c106eb265802b0db161101d376442b2aaf33c08.camel@rendec.net> Subject: Re: [PATCH 0/3] irqchip/gic-v3: Lifetime and range fixes in the GICv3 and ITS drivers From: Radu Rendec To: Fuad Tabba , Marc Zyngier , Thomas Gleixner Cc: Kemeng Shi , Will Deacon , Fuad Tabba , stable@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Date: Sat, 19 Sep 2026 10:58:16 -0400 In-Reply-To: <20260908142632.2795308-1-fuad.tabba@linux.dev> References: <20260908142632.2795308-1-fuad.tabba@linux.dev> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260919_075827_104117_423EE9DD X-CRM114-Status: GOOD ( 16.46 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, 2026-09-08 at 15:26 +0100, Fuad Tabba wrote: > Hi folks, >=20 > Three fixes to the GICv3 and ITS drivers, from reviewing the GIC series > floating around and chasing down Sashiko's reports. >=20 > The first releases the partition node that gic_irq_get_fwspec_info() > takes from of_find_node_by_phandle() and never puts. Sashiko raised it > on an of/irq patch of mine, and I said a fix was forthcoming [1]. >=20 > The second widens the per-device MSI clamp, which truncates to zero when > GITS_TYPER.ID_bits is at its maximum and then denies every MSI on that > ITS. I couldn't find an implementation that reports that maximum, so > this is one value at the edge rather than something anyone is hitting. > It carries Cc: stable because the commit it fixes was itself > backported, so drop the tag if you'd rather. >=20 > The third clears vpt_page once its_vpe_teardown() has freed it, so the > NULL guard holds if teardown runs again on the same vPE. >=20 > Based on Linux 7.3-rc2 (df2908090cda3). >=20 > Cheers, > /fuad >=20 > [1] https://lore.kernel.org/all/CA+EHjTx7eP_30vP47=3DUFk_wMAut-2uf+2DF-MZ= qn2SLE_k-8qg@mail.gmail.com/ >=20 > Fuad Tabba (3): > =C2=A0 irqchip/gic-v3: Release the partition node in > =C2=A0=C2=A0=C2=A0 gic_irq_get_fwspec_info() > =C2=A0 irqchip/gic-v3-its: Don't clamp nvecs to zero when id_bits is 32 > =C2=A0 irqchip/gic-v3-its: Clear vpt_page after freeing the pending table >=20 > =C2=A0drivers/irqchip/irq-gic-v3-its.c | 3 ++- > =C2=A0drivers/irqchip/irq-gic-v3.c=C2=A0=C2=A0=C2=A0=C2=A0 | 7 ++++--- > =C2=A02 files changed, 6 insertions(+), 4 deletions(-) >=20 >=20 > base-commit: df2908090cda368b01ff43709f51890076c56157 Reviewed-by: Radu Rendec