From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1] arm64/sve: Discard stale CPU state when handling SVE traps
Date: Fri, 6 Dec 2024 12:11:24 -0500 [thread overview]
Message-ID: <20241206095940-7f452f166e2e0511@stable.kernel.org> (raw)
In-Reply-To: <20241206132206.143543-1-broonie@kernel.org>
[ Sasha's backport helper bot ]
Hi,
Found matching upstream commit: 751ecf6afd6568adc98f2a6052315552c0483d18
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 51d11ea0250d)
6.1.y | Not found
Note: The patch differs from the upstream commit:
---
1: 751ecf6afd656 ! 1: b773f808e9357 arm64/sve: Discard stale CPU state when handling SVE traps
@@ Commit message
Reviewed-by: Mark Rutland <mark.rutland@arm.com>
Link: https://lore.kernel.org/r/20241030-arm64-fpsimd-foreign-flush-v1-1-bd7bd66905a2@kernel.org
Signed-off-by: Will Deacon <will@kernel.org>
+ [Backported to 6.1 -- broonie]
+ (cherry picked from commit 751ecf6afd6568adc98f2a6052315552c0483d18)
## arch/arm64/kernel/fpsimd.c ##
@@ arch/arm64/kernel/fpsimd.c: static void sve_init_regs(void)
+ fpsimd_bind_task_to_cpu();
} else {
fpsimd_to_sve(current);
- current->thread.fp_type = FP_STATE_SVE;
+ fpsimd_flush_task_state(current);
}
}
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
prev parent reply other threads:[~2024-12-06 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 13:22 [PATCH 6.1] arm64/sve: Discard stale CPU state when handling SVE traps Mark Brown
2024-12-06 17:11 ` Sasha Levin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241206095940-7f452f166e2e0511@stable.kernel.org \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.