Thanks, Rajesh Dasari.

On Thu, Aug 10, 2023 at 5:19 PM Thadeu Lima de Souza Cascardo cascardo@canonical.com wrote:

On Thu, Aug 10, 2023 at 12:58:53PM +0300, RAJESH DASARI wrote:

...

Hi ,

We are noticing the below warning in the latest 5.4.252 kernel bootup logs.

WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:878 get_xsave_addr+0x83/0x90

and relevant call trace in the logs , after updating to kernel 5.4.252.

I see that issue is due to this commit https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v...

This is seen in the qemu instance which is emulating the host cpu and was deployed on Intel(R) Xeon(R) Gold 5218 processor.

I revert the commit and there is no WARNING and call trace in the logs , Is this issue already reported and a fix is available? Could you please provide your inputs.

Regards, Rajesh.

Does applying b3607269ff57 ("x86/pkeys: Revert a5eff7259790 ("x86/pkeys: Add PKRU value to init_fpstate")") fixes it for you?

Thanks for the quick response. Yes this patch works, WARNING is not seen now. any plans to backport this patch to 5.4.x kernel releases?

Cascardo.