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 666E7CF8543 for ; Wed, 2 Oct 2024 22:18:41 +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:Content-Type:MIME-Version: Message-ID:Date:References:In-Reply-To:Subject:Cc:To:From:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=jFjZeiFVpmHVjg0rdNh6hIED5M51QQAMChgDBPTcq2k=; b=cTmdXxFn6l/HkeH39Gt9HGDM4k rlJAE7/gjM16J1w0OZTukw3T5gKhK4y9+oIoMn6O6wWm8BIyTIylwivGDE8DZMWs8SdhbsVKV3hkX hAUfvAzm3WU7+AuUoknVb1IXQX0oL6nRX4OouN0haSqsvtIvzRCSOcg06DC5PjzsF4arn5j5o7un8 GSZ0Q+x+KOY6LfZoLLkzDZV1dXvyvm37VlnLcjO1cwSYsxJqTIKDozVmR6Z/FoFxVxoPZ2pCx0d7x nCWXn/hY0KfYwHf2vtS2oZp0/gsqDRpqBwPeZjqyahsao5t+TZcB80G5uTKjsEEzia4lcdMtEWST1 RH426hdA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1sw7fw-00000007d6p-3a3i; Wed, 02 Oct 2024 22:18:28 +0000 Received: from galois.linutronix.de ([2a0a:51c0:0:12e:550::1]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1sw7ec-00000007cvr-1o2h for linux-arm-kernel@lists.infradead.org; Wed, 02 Oct 2024 22:17:10 +0000 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1727907422; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=jFjZeiFVpmHVjg0rdNh6hIED5M51QQAMChgDBPTcq2k=; b=n35SjfgWXhPe4Ya9YJz1AieiQfL3DkXpxCk2Z4WisZBKx+wUE+AKS0X+qKGmkP9VV8kOJa pDTFvS5RisMxRO5DrDRQ/hYf9mz7+biK1CYjk61npZdTBp0/WJnO8Xhn/Ac/hhjSSili1m Pru1mB8FmxVxTKqsqRGQKhWFzS1gHh+BZMsN3zox2uHRwrjgEEucrpLFFSS3Jeddv6VJeQ QTf1R2z8o6e6kEy2DtyiFh4fBBTgQqsZT6IOZzsP/rjBl5mv07EIVXFz/i+p4i/0/LuI1l 1Tm60F3S6VnxNI2iYkEiDlN7/n6XExQLYSklmH0vpQuOsmJO+MnCM2Kp/MI39Q== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1727907422; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=jFjZeiFVpmHVjg0rdNh6hIED5M51QQAMChgDBPTcq2k=; b=Wx81KmxvDq9BKJxN0r990aUW4SiMEGRYtT3TsO3IpmFdRk7LD0nokdzjPUx5ZEng7mDk4R 2iL3ekJU0tkEPZAA== To: Marc Zyngier , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: Kunkun Jiang Subject: Re: [PATCH] irqchip/gic-v4: Don't allow a VMOVP on a dying VPE In-Reply-To: <20241002204959.2051709-1-maz@kernel.org> References: <20241002204959.2051709-1-maz@kernel.org> Date: Thu, 03 Oct 2024 00:17:02 +0200 Message-ID: <87zfnmup41.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20241002_151707_729284_9F405719 X-CRM114-Status: GOOD ( 11.08 ) 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 Wed, Oct 02 2024 at 21:49, Marc Zyngier wrote: > Kunkun Jiang reports that there is a small window of opportunity for > userspace to force a change of affinity for a VPE while the VPE has > already been unmapped, but the corresponding doorbell interrupt still > visible in /proc/irq/. > > Plug the race by checking the value of vmapp_count, which tracks whether > the VPE is mapped ot not, and returning an error in this case. > > This involves making vmapp_count common to both GICv4.1 and its v4.0 > ancestor. > > Reported-by: Kunkun Jiang > Signed-off-by: Marc Zyngier > Link: https://lore.kernel.org/r/c182ece6-2ba0-ce4f-3404-dba7a3ab6c52@huawei.com I assume this wants a Fixes: tag and a cc: stable, no? Thanks, tglx