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;
From:   Catalin Marinas <catalin.marinas@arm.com>
To:     Will Deacon <will@kernel.org>, Mark Brown <broonie@kernel.org>
Cc:     David Spickett <David.Spickett@arm.com>,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        stable@vger.kernel.org
Subject: Re: [PATCH] arm64/fpsimd: Clear SME state in the target task when setting the VL
Date:   Thu,  3 Aug 2023 18:28:05 +0100
Message-Id: <169108367979.2495938.18347411845620974052.b4-ty@arm.com>
In-Reply-To: <20230803-arm64-fix-ptrace-tif-sme-v1-1-88312fd6fbfd@kernel.org>
References: <20230803-arm64-fix-ptrace-tif-sme-v1-1-88312fd6fbfd@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 03 Aug 2023 00:46:39 +0100, Mark Brown wrote:
> When setting SME vector lengths we clear TIF_SME to reenable SME traps,
> doing a reallocation of the backing storage on next use. We do this using
> clear_thread_flag() which operates on the current thread, meaning that when
> setting the vector length via ptrace we may both not force traps for the
> target task and force a spurious flush of any SME state that the tracing
> task may have.
> 
> [...]

Applied to arm64 (for-next/fixes), thanks!

[1/1] arm64/fpsimd: Clear SME state in the target task when setting the VL
      https://git.kernel.org/arm64/c/c9bb40b7f786

-- 
Catalin