From: Naveen N Rao <naveen@kernel.org>
To: Gal Pressman <gal@nvidia.com>
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Dragos Tatulea <dtatulea@nvidia.com>
Subject: Re: [PATCH v2 1/2] KVM: SVM: Fix UBSAN warning when reading avic parameter
Date: Thu, 26 Feb 2026 11:05:01 +0530 [thread overview]
Message-ID: <aZ_bb_1cSwqYn1W6@blrnaveerao1> (raw)
In-Reply-To: <20260225145050.2350278-2-gal@nvidia.com>
On Wed, Feb 25, 2026 at 04:50:49PM +0200, Gal Pressman wrote:
> The avic parameter is stored as an int to support the special value -1
> (AVIC_AUTO_MODE), but the cited commit changed it from bool to int while
> keeping param_get_bool() as the getter function.
> This causes UBSAN to report "load of value 255 is not a valid value for
> type '_Bool'" when the parameter is read via sysfs.
>
> The issue happens in two scenarios:
>
> 1. During module load: There's a time window between when module
> parameters are registered, and when avic_hardware_setup() runs to
> resolve the value, where the value is -1.
>
> 2. On non-AMD systems: On non-AMD hardware, the kvm_is_svm_supported()
> check returns early. The avic_hardware_setup() function never runs,
> so avic remains -1.
>
> Fix that by implementing a getter function that properly reads and
> converts the -1 value into a string.
>
> Triggered by sos report:
> UBSAN: invalid-load in kernel/params.c:323:33
> load of value 255 is not a valid value for type '_Bool'
> CPU: 0 UID: 0 PID: 4667 Comm: sos Not tainted 6.19.0-rc5net_mlx5_1e86836 #1 NONE
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014
> Call Trace:
> <TASK>
> dump_stack_lvl+0x69/0xa0
> ubsan_epilogue+0x5/0x2b
> __ubsan_handle_load_invalid_value.cold+0x47/0x4c
> ? lock_acquire+0x219/0x2c0
> param_get_bool.cold+0xf/0x14
> param_attr_show+0x51/0x80
> module_attr_show+0x19/0x30
> sysfs_kf_seq_show+0xac/0xf0
> seq_read_iter+0x100/0x410
> copy_splice_read+0x1b4/0x360
> splice_direct_to_actor+0xbd/0x270
> ? wait_for_space+0xb0/0xb0
> do_splice_direct+0x72/0xb0
> ? propagate_umount+0x870/0x870
> do_sendfile+0x3a3/0x470
> __x64_sys_sendfile64+0x5e/0xe0
> do_syscall_64+0x70/0x8c0
> entry_SYSCALL_64_after_hwframe+0x4b/0x53
>
> Fixes: ca2967de5a5b ("KVM: SVM: Enable AVIC by default for Zen4+ if x2AVIC is support")
> Reviewed-by: Dragos Tatulea <dtatulea@nvidia.com>
> Signed-off-by: Gal Pressman <gal@nvidia.com>
> ---
> arch/x86/kvm/svm/avic.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
LGTM.
Reviewed-by: Naveen N Rao (AMD) <naveen@kernel.org>
- Naveen
next prev parent reply other threads:[~2026-02-26 5:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 14:50 [PATCH v2 0/2] KVM: x86: Fix UBSAN bool warnings in module parameters Gal Pressman
2026-02-25 14:50 ` [PATCH v2 1/2] KVM: SVM: Fix UBSAN warning when reading avic parameter Gal Pressman
2026-02-26 5:35 ` Naveen N Rao [this message]
2026-02-25 14:50 ` [PATCH v2 2/2] KVM: x86/mmu: Fix UBSAN warning when reading nx_huge_pages parameter Gal Pressman
2026-03-05 17:08 ` [PATCH v2 0/2] KVM: x86: Fix UBSAN bool warnings in module parameters Sean Christopherson
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=aZ_bb_1cSwqYn1W6@blrnaveerao1 \
--to=naveen@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dtatulea@nvidia.com \
--cc=gal@nvidia.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@kernel.org \
--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
all inboxes | Powered by JetHome®