From: Ingo Molnar <mingo@kernel.org>
To: Akihiro Suda <suda.gitsendemail@gmail.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
suda.kyoto@gmail.com, regressions@lists.linux.dev,
aruna.ramakrishna@oracle.com, tglx@linutronix.de,
Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Subject: Re: [PATCH v2] x86: disable PKU when running on Apple Virtualization
Date: Thu, 13 Mar 2025 18:02:16 +0100 [thread overview]
Message-ID: <Z9MPmA-myNZxcc-E@gmail.com> (raw)
In-Reply-To: <20250312100926.34954-1-akihiro.suda.cz@hco.ntt.co.jp>
* Akihiro Suda <suda.gitsendemail@gmail.com> wrote:
> OSPKE seems broken on Apple Virtualization.
>
> WARNING: CPU: 0 PID: 1 at arch/x86/kernel/fpu/xstate.c:1003 get_xsave_addr_user+0x28/0x40
> (...)
> Call Trace:
> <TASK>
> ? get_xsave_addr_user+0x28/0x40
> ? __warn.cold+0x8e/0xea
> ? get_xsave_addr_user+0x28/0x40
> ? report_bug+0xff/0x140
> ? handle_bug+0x3b/0x70
> ? exc_invalid_op+0x17/0x70
> ? asm_exc_invalid_op+0x1a/0x20
> ? get_xsave_addr_user+0x28/0x40
> copy_fpstate_to_sigframe+0x1be/0x380
> ? __put_user_8+0x11/0x20
> get_sigframe+0xf1/0x280
> x64_setup_rt_frame+0x67/0x2c0
> arch_do_signal_or_restart+0x1b3/0x240
> syscall_exit_to_user_mode+0xb0/0x130
> do_syscall_64+0xab/0x1a0
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> Tested on macOS 13.5.1 running on MacBook Pro 2020 with
> Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz.
>
> Fixes: 70044df250d0 ("x86/pkeys: Update PKRU to enable all pkeys before XSAVE")
> Link: https://lore.kernel.org/regressions/CAG8fp8QvH71Wi_y7b7tgFp7knK38rfrF7rRHh-gFKqeS0gxY6Q@mail.gmail.com/T/#u
> Link: https://github.com/lima-vm/lima/issues/3334
> Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
> ---
> v2: check oem_table_id rather than oem_id for better robustness
So this is rather weird, but I've applied the quirk as it upgrades
broken guest side code into a boot time warning.
> + /*
> + * OSPKE seems broken on Apple Virtualization.
> + * https://lore.kernel.org/regressions/CAG8fp8QvH71Wi_y7b7tgFp7knK38rfrF7rRHh-gFKqeS0gxY6Q@mail.gmail.com/T/#u
> + *
> + * TODO: conditionally enable pku depending on the DMI BIOS version when Apple
> + * fixes the issue.
> + *
> + * However, this would be still not enough because DMI is missing when vmlinuz
> + * is directly loaded into VM.
> + */
> + if (!memcmp(acpi_gbl_FADT.header.oem_table_id, "Apple Vz", 8)) {
> + pr_info("pku: disabled on Apple Virtualization platform (Intel) due to a bug\n");
> + pku_disabled = true;
> + }
Note that I updated the comments here (the git log gives enough
information), plus enclosed this into #ifdef CONFIG_ACPI, as
acpi_gbl_FADT is not available on !CONFIG_ACPI builds.
Thanks,
Ingo
next prev parent reply other threads:[~2025-03-13 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG8fp8Qdmt9vLk=8ORccY5B+ec1huhazXG4PBaNyLEkq31HDjw@mail.gmail.com>
2025-03-12 10:09 ` [PATCH v2] x86: disable PKU when running on Apple Virtualization Akihiro Suda
2025-03-12 10:21 ` Greg KH
2025-03-13 17:02 ` Ingo Molnar [this message]
2025-03-13 23:59 ` Akihiro Suda
2025-03-13 17:11 ` [tip: x86/urgent] x86/pkeys: Disable " tip-bot2 for Akihiro Suda
2025-03-14 6:26 ` [PATCH v2] x86: disable " kernel test robot
2025-03-14 6:26 ` kernel test robot
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=Z9MPmA-myNZxcc-E@gmail.com \
--to=mingo@kernel.org \
--cc=akihiro.suda.cz@hco.ntt.co.jp \
--cc=aruna.ramakrishna@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=suda.gitsendemail@gmail.com \
--cc=suda.kyoto@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox