From: "Jürgen Groß" <jgross@suse.com>
To: Alexey Dobriyan <adobriyan@gmail.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] xen, pvh: fix unbootable VMs (PVH + KASAN)
Date: Fri, 2 Aug 2024 07:44:11 +0200 [thread overview]
Message-ID: <242b327a-9244-411c-8d3e-7b860464f8f6@suse.com> (raw)
In-Reply-To: <a9f505a6-fd31-4cfa-a193-d21638bb14f1@p183>
On 01.08.24 21:16, Alexey Dobriyan wrote:
> Uninstrument arch/x86/platform/pvh/enlighten.c: KASAN is not setup
> _this_ early in the boot process.
>
> Steps to reproduce:
>
> make allnoconfig
> make sure CONFIG_AMD_MEM_ENCRYPT is disabled
> AMD_MEM_ENCRYPT independently uninstruments lib/string.o
> so PVH boot code calls into uninstrumented memset() and
> memcmp() which can make the bug disappear depending on
> the compiler.
> enable CONFIG_PVH
> enable CONFIG_KASAN
> enable serial console
> this is fun exercise if you never done it from nothing :^)
>
> make
>
> qemu-system-x86_64 \
> -enable-kvm \
> -cpu host \
> -smp cpus=1 \
> -m 4096 \
> -serial stdio \
> -kernel vmlinux \
> -append 'console=ttyS0 ignore_loglevel'
>
> Messages on serial console will easily tell OK kernel from unbootable
> kernel. In bad case qemu hangs in an infinite loop stroboscoping
> "SeaBIOS" message.
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Acked-by: Juergen Gross <jgross@suse.com>
Juergen
next prev parent reply other threads:[~2024-08-02 5:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 19:16 Alexey Dobriyan
2024-08-02 5:44 ` Jürgen Groß [this message]
2024-08-02 8:50 ` [PATCH 2/3] x86/cpu: fix unbootable VMs by inlining memcmp in hypervisor_cpuid_base Alexey Dobriyan
2024-08-02 12:56 ` Thomas Gleixner
2024-08-02 13:25 ` Nikolay Borisov
2024-08-02 13:29 ` Thomas Gleixner
2024-08-02 8:53 ` [PATCH 3/3] xen, pvh: fix unbootable VMs by inlining memset in xen_prepare_pvh Alexey Dobriyan
2024-08-02 12:57 ` Thomas Gleixner
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=242b327a-9244-411c-8d3e-7b860464f8f6@suse.com \
--to=jgross@suse.com \
--cc=adobriyan@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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®