From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id F20F843148C for ; Thu, 16 Jul 2026 16:48:22 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784220512; cv=none; b=aMSDcQN2SZTCvv4n+EO3YGjQf2bJ1i2V6YyofmGiEl0BYMNc4Owv/fKpl1ixAhQ2/wr6GLIKAYlDUYzT1PLerXMXephTdYKwDDfpNF8QY3XW29vH6US6Fy/3Fm3kSc30nTkpMpev+XOFz5+xb1UjxcKABJqhnU0ZPSNFgy0eV6c= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784220512; c=relaxed/simple; bh=sTdKmc6t7oHgpas+DAqDZoE5T/8ahRpCqSq1TpISMys=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=E+iCRiUIbb3FZ4qX9AsCuD5Afq9MayMck/5x/ZbcwqswZDESG3itV9WDG+xkE4r/H5PTzU9yfPqzokaKJA3vWZJnEudPGbF24BEu42c0XMeotCb92hjyQUQkEXhnA9rzp/YilE2NFS070S5XmvWrmGpWQ6E5vHDKiCSV6VJgbww= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Sn672RZU; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Sn672RZU" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 802371F00A3F; Thu, 16 Jul 2026 16:48:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1784220500; bh=7aYWR7TGdNYjkLxVXmWuRVSKIIhb67yRGihsaVkcH8M=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=Sn672RZUGNRtO4T1GSIneL/kHKYtfDDk64OO5GlmkDaqbu5iCJ/N1G7j5v0xnaQzf Uq0N9bXROGEG7HTgtXdZw/zI0ui0yPA9LO/0iG6bKEoLwS/5KtU6v84+oKvMF6v8hm 62h3ZuBWMJd0b0fZZBKSyo8l0NXgshaPB5iG48/Kt7HXG+IJuUbyys3i8fSepffTK5 w7V6d6YGyhTUesp9R/KzSfRc2zn76aqp7AGsBFmwhnNrAl2UZRctMHFReqmskyXftV xIEpCGsQxoMlqOjVOFbLq2rN4pN8D/B5cZqpdXwq3CY5Y8vDOSDIi+xrjET02gjMy/ 4S5b1QBI+rxhw== From: Will Deacon To: linux-arm-kernel@lists.infradead.org, Will Deacon Cc: catalin.marinas@arm.com, kernel-team@android.com, linux-kernel@vger.kernel.org, Kees Cook , Jinjie Ruan , Mark Rutland , Yiqi Sun Subject: Re: [PATCH v2] arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates Date: Thu, 16 Jul 2026 17:48:01 +0100 Message-ID: <178420908877.33796.2351583216856259313.b4-ty@kernel.org> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260716120640.6590-1-will@kernel.org> References: <20260716120640.6590-1-will@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit On Thu, 16 Jul 2026 13:06:39 +0100, Will Deacon wrote: > When seccomp support was originally added to arm64 in a1ae65b21941 > ("arm64: add seccomp support"), seccomp was erroneously called _before_ > the ptrace syscall-enter-stop and therefore the tracer could trivially > manipulate the syscall register state after the seccomp check had > passed. This was subsequently fixed in a5cd110cb836 ("arm64/ptrace: run > seccomp after ptrace") by moving the seccomp check after the tracer has > run. Unfortunately, a decade later, that fix has been reported to be > incomplete. > > [...] Applied to arm64 (for-next/fixes), thanks! [1/1] arm64: syscall: Ensure saved x0 is kept in-sync with tracer updates https://git.kernel.org/arm64/c/e057b9477232 Cheers, -- Will https://fixes.arm64.dev https://next.arm64.dev https://will.arm64.dev