From: Richard Weinberger <richard@nod.at>
To: YiFei Zhu <zhuyifei1999@gmail.com>
Cc: subashab <subashab@codeaurora.org>,
Johannes Berg <johannes@sipsolutions.net>,
anton ivanov <anton.ivanov@cambridgegreys.com>,
Jeff Dike <jdike@addtoit.com>,
linux-um <linux-um@lists.infradead.org>,
stranche <stranche@codeaurora.org>
Subject: Re: UML kernel panic on initialization
Date: Wed, 14 Jul 2021 00:14:20 +0200 (CEST) [thread overview]
Message-ID: <756593647.23483.1626214460129.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CABqSeARhjVWwX3YnaUZtvn1-8a6c46oxCj6BnpDirVMP9jjEgA@mail.gmail.com>
----- Ursprüngliche Mail -----
> Von: "YiFei Zhu" <zhuyifei1999@gmail.com>
> An: "subashab" <subashab@codeaurora.org>
> CC: "Johannes Berg" <johannes@sipsolutions.net>, "richard" <richard@nod.at>, "anton ivanov"
> <anton.ivanov@cambridgegreys.com>, "Jeff Dike" <jdike@addtoit.com>, "linux-um" <linux-um@lists.infradead.org>,
> "stranche" <stranche@codeaurora.org>
> Gesendet: Dienstag, 13. Juli 2021 22:52:43
> Betreff: Re: UML kernel panic on initialization
> On Tue, Jul 13, 2021 at 3:00 PM <subashab@codeaurora.org> wrote:
>>
>> > Wasn't compatible with my system ... can you describe the host system?
>> >
>> > johannes
>>
>> Its an Intel 8th gen i7 with Ubuntu 16.04 LTS.
>> Kernel version is 4.15.0-70-generic.
>> gcc version is 5.4.
>
> FWIW, for me, compiling UML with defconfig inside a Ubuntu 16.04
> docker is enough to produce a binary that could trigger a crash even
> outside docker, using hostfs root mount (so no special ld.so).
>
> This is some sort of compiler difference.
Exactly. :-)
Please see Johannes' patch:
http://lists.infradead.org/pipermail/linux-um/2021-July/001571.html
Thanks,
//richard
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2021-07-13 22:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 21:00 UML kernel panic on initialization subashab
2021-07-11 20:27 ` YiFei Zhu
2021-07-12 18:19 ` subashab
2021-07-13 4:04 ` YiFei Zhu
2021-07-13 13:50 ` Anton Ivanov
2021-07-13 14:03 ` Richard Weinberger
2021-07-13 18:02 ` subashab
2021-07-13 18:32 ` Johannes Berg
2021-07-13 18:54 ` subashab
2021-07-13 19:17 ` Johannes Berg
2021-07-13 20:00 ` subashab
2021-07-13 20:52 ` YiFei Zhu
2021-07-13 22:14 ` Richard Weinberger [this message]
2021-07-13 17:47 ` subashab
2021-07-13 19:22 ` Johannes Berg
2021-07-13 19:26 ` Johannes Berg
2021-07-13 19:28 ` Johannes Berg
2021-07-13 20:40 ` subashab
2021-07-13 20:41 ` Johannes Berg
2021-07-13 20:16 ` subashab
2021-07-13 20:07 ` subashab
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=756593647.23483.1626214460129.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=anton.ivanov@cambridgegreys.com \
--cc=jdike@addtoit.com \
--cc=johannes@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=stranche@codeaurora.org \
--cc=subashab@codeaurora.org \
--cc=zhuyifei1999@gmail.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.