summaryrefslogtreecommitdiffstats
path: root/CREDITS
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2021-09-09 17:53:56 +0100
committerCatalin Marinas <catalin.marinas@arm.com>2021-09-16 17:34:46 +0100
commite35ac9d0b56e9efefaeeb84b635ea26c2839ea86 (patch)
tree27983ab5921bd9b59ad51c4b4a95eadd5b7c2ed4 /CREDITS
parent6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f (diff)
downloadlinux-stable-e35ac9d0b56e9efefaeeb84b635ea26c2839ea86.tar.gz
linux-stable-e35ac9d0b56e9efefaeeb84b635ea26c2839ea86.tar.bz2
linux-stable-e35ac9d0b56e9efefaeeb84b635ea26c2839ea86.zip
arm64/sve: Use correct size when reinitialising SVE state
When we need a buffer for SVE register state we call sve_alloc() to make sure that one is there. In order to avoid repeated allocations and frees we keep the buffer around unless we change vector length and just memset() it to ensure a clean register state. The function that deals with this takes the task to operate on as an argument, however in the case where we do a memset() we initialise using the SVE state size for the current task rather than the task passed as an argument. This is only an issue in the case where we are setting the register state for a task via ptrace and the task being configured has a different vector length to the task tracing it. In the case where the buffer is larger in the traced process we will leak old state from the traced process to itself, in the case where the buffer is smaller in the traced process we will overflow the buffer and corrupt memory. Fixes: bc0ee4760364 ("arm64/sve: Core task context handling") Cc: <stable@vger.kernel.org> # 4.15.x Signed-off-by: Mark Brown <broonie@kernel.org> Link: https://lore.kernel.org/r/20210909165356.10675-1-broonie@kernel.org Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions