From: Sean Christopherson <seanjc@google.com>
To: Jan Stancek <jstancek@redhat.com>
Cc: Bruno Goncalves <bgoncalv@redhat.com>, kvm <kvm@vger.kernel.org>,
"Bonzini, Paolo" <pbonzini@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
CKI Project <cki-project@redhat.com>, Li Wang <liwang@redhat.com>
Subject: Re: RIP: 0010:param_get_bool.cold+0x0/0x2 - LTP read_all_sys - 5.17.0
Date: Thu, 31 Mar 2022 18:45:36 +0000 [thread overview]
Message-ID: <YkX20LtaENdOOYxi@google.com> (raw)
In-Reply-To: <YkXv0NoBjLBYBzX8@google.com>
On Thu, Mar 31, 2022, Sean Christopherson wrote:
> On Wed, Mar 30, 2022, Jan Stancek wrote:
> > +CC kvm
> >
> > Issue seems to be that nx_huge_pages is not initialized (-1) and
> > attempted to be used as boolean when reading
> > /sys/module/kvm/parameters/nx_huge_pages
>
> Ugh, CONFIG_UBSAN_BOOL=y complains about a bool not being 0 or 1. What a pain.
Side topic, any idea why your traces don't have the UBSAN output? I verified
that it's not a panic_on_warn thing. Having the UBSAN output in future bug reports
would be very helpful.
[ 13.150244] ================================================================================
[ 13.150780] UBSAN: invalid-load in kernel/params.c:320:33
[ 13.151192] load of value 255 is not a valid value for type '_Bool'
[ 13.152079] ================================================================================
next prev parent reply other threads:[~2022-03-31 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 14:09 RIP: 0010:param_get_bool.cold+0x0/0x2 - LTP read_all_sys - 5.17.0 Bruno Goncalves
2022-03-30 12:46 ` Jan Stancek
2022-03-31 18:15 ` Sean Christopherson
2022-03-31 18:45 ` Sean Christopherson [this message]
2022-03-31 19:27 ` Jan Stancek
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=YkX20LtaENdOOYxi@google.com \
--to=seanjc@google.com \
--cc=bgoncalv@redhat.com \
--cc=cki-project@redhat.com \
--cc=jstancek@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwang@redhat.com \
--cc=pbonzini@redhat.com \
/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.