Received-SPF: pass (google.com: domain of linux-kernel+bounces-30075-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>
Cc: kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	stable@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Dave Martin <dave.martin@arm.com>
Subject: Re: [PATCH] arm64/sme: Always exit sme_alloc() early with existing storage
Date: Thu, 18 Jan 2024 12:02:25 +0000
Message-Id: <170557595437.3201963.17750438476514444044.b4-ty@kernel.org>
In-Reply-To: <20240115-arm64-sme-flush-v1-1-7472bd3459b7@kernel.org>
References: <20240115-arm64-sme-flush-v1-1-7472bd3459b7@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

On Mon, 15 Jan 2024 20:15:46 +0000, Mark Brown wrote:
> When sme_alloc() is called with existing storage and we are not flushing we
> will always allocate new storage, both leaking the existing storage and
> corrupting the state. Fix this by separating the checks for flushing and
> for existing storage as we do for SVE.
> 
> Callers that reallocate (eg, due to changing the vector length) should
> call sme_free() themselves.
> 
> [...]

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

[1/1] arm64/sme: Always exit sme_alloc() early with existing storage
      https://git.kernel.org/arm64/c/dc7eb8755797

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev