From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: oss-security@lists.openwall.com,
"debian-powerpc@lists.debian.org"
<debian-powerpc@lists.debian.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Linux kernel: powerpc: KVM guest can trigger host crash on Power8
Date: Wed, 27 Oct 2021 13:09:47 +0200 [thread overview]
Message-ID: <c21c7a0e-95f1-e6d2-a04c-fb99d801e8da@physik.fu-berlin.de> (raw)
In-Reply-To: <874k92bubv.fsf@mpe.ellerman.id.au>
Hi Michael!
On 10/27/21 13:06, Michael Ellerman wrote:
> John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:
>> Hi Michael!
>>
>> On 10/27/21 07:30, Michael Ellerman wrote:
>>> I did test the repro case you gave me before (in the bugzilla), which
>>> was building glibc, that passes for me with a patched host.
>>
>> Did you manage to crash the unpatched host?
>
> Yes, the parallel builds of glibc you described crashed the unpatched
> host 100% reliably for me.
OK, that is very good news!
> I also have a standalone reproducer I'll send you.
Thanks, that would be helpful!
>> Also, I'll try a kernel from git with Debian's config.
>>
>>> I guess we have yet another bug.
>>>
>>> I tried the following in a debian BE VM and it completed fine:
>>>
>>> $ dget -u http://ftp.debian.org/debian/pool/main/g/git/git_2.33.1-1.dsc
>>> $ sbuild -d sid --arch=powerpc --no-arch-all git_2.33.1-1.dsc
>>>
>>> Same for ppc64.
>>>
>>> And I also tried both at once, repeatedly in a loop.
>>
>> Did you try building gcc-11 for powerpc and ppc64 both at once?
>
> No, I will try that now.
OK, great!
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2021-10-27 11:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 11:18 Linux kernel: powerpc: KVM guest can trigger host crash on Power8 Michael Ellerman
2021-10-26 8:48 ` John Paul Adrian Glaubitz
2021-10-27 5:29 ` Nicholas Piggin
2021-10-27 5:30 ` Michael Ellerman
2021-10-27 10:03 ` John Paul Adrian Glaubitz
2021-10-27 11:06 ` Michael Ellerman
2021-10-27 11:09 ` John Paul Adrian Glaubitz [this message]
2021-10-28 6:39 ` Michael Ellerman
2021-10-28 11:20 ` John Paul Adrian Glaubitz
2021-10-28 14:05 ` John Paul Adrian Glaubitz
2021-10-28 14:15 ` John Paul Adrian Glaubitz
2021-11-01 17:36 ` Michal Suchánek
2021-10-29 0:41 ` Nicholas Piggin
2021-10-29 12:33 ` John Paul Adrian Glaubitz
2021-11-01 17:43 ` Michal Suchánek
2021-10-30 7:19 ` John Paul Adrian Glaubitz
2021-11-01 6:53 ` Michael Ellerman
2021-11-01 7:37 ` John Paul Adrian Glaubitz
2021-11-01 17:20 ` John Paul Adrian Glaubitz
2022-01-04 13:00 ` John Paul Adrian Glaubitz
2022-01-06 10:58 ` Michael Ellerman
2022-01-07 11:20 ` John Paul Adrian Glaubitz
2022-01-09 22:17 ` John Paul Adrian Glaubitz
2022-01-13 0:17 ` John Paul Adrian Glaubitz
2022-01-26 20:21 ` John Paul Adrian Glaubitz
2022-01-27 15:50 ` Mike
2021-10-28 13:52 ` John Paul Adrian Glaubitz
2021-10-28 14:00 ` John Paul Adrian Glaubitz
2021-10-28 3:58 ` [oss-security] " Salvatore Bonaccorso
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=c21c7a0e-95f1-e6d2-a04c-fb99d801e8da@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oss-security@lists.openwall.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).