APPLIED: [SRU][F][PATCH 1/1] Fix boot test warning for log_check

[Roxana Nicolescu]

On 10/08/2023 17:56, Roxana Nicolescu wrote:
> BugLink: https://bugs.launchpad.net/bugs/2031022
>
> SRU Justification
>
> [Impact]
>
> Gather Data Sampling, affecting Intel processors and assigned CVE-2022-40982
> introduced this warning.The fix is on microcode, but part of the mitigation on
> the kernel side is to detect if the microcode update is not there and disable
> AVX in case it's supported. This needed some reshuffle during initialization so
> that turning off AVX was possible without it being too late, which also moved
> the FPU initialization. See commit
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.252&id=6e60443668978131a442df485db3deccb31d5651
>
> This causes the following warning during boot:
> CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x98/0xb0
>
> [Fix]
> This commit seems to fix the warning
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.14.321&id=b3607269ff57
>
> [Test plan]
> Booted locally and no warning shown.
>
> [Regression potentials]
> We may see issue during FPU init.
>
> Thomas Gleixner (1):
>    x86/pkeys: Revert a5eff7259790 ("x86/pkeys: Add PKRU value to init_fpstate")
>
>   arch/x86/kernel/cpu/common.c | 5 -----
>   arch/x86/mm/pkeys.c          | 6 ------
>   2 files changed, 11 deletions(-)
>
Applied to focal:master-next. Thanks!