From: Johannes Berg <johannes@sipsolutions.net>
To: subashab@codeaurora.org, jdike@addtoit.com, richard@nod.at,
anton.ivanov@cambridgegreys.com, linux-um@lists.infradead.org
Subject: Re: UML kernel panic on initialization
Date: Tue, 13 Jul 2021 21:28:44 +0200 [thread overview]
Message-ID: <17bc19ae635b61d50627fd1601b0ab12b5128999.camel@sipsolutions.net> (raw)
In-Reply-To: <8c377addaa42a7dd3bbe047e1f744a51103e6ff2.camel@sipsolutions.net>
On Tue, 2021-07-13 at 21:26 +0200, Johannes Berg wrote:
> On Tue, 2021-07-13 at 21:22 +0200, Johannes Berg wrote:
> > On Sat, 2021-07-10 at 15:00 -0600, subashab@codeaurora.org wrote:
> > >
> > > I have reverted the following patches (to allow for a clean revert)
> > > and I don't see the panic anymore -
> > >
> > > bfc58e2b98e99737409cd9f4d86a79677c5b887c
> > > dc01a3b9db43abf95b801c9694980777a329e303
> > > 9f0b4807a44ff81cf59421c8a86641efec586610
> > > 84b2789d61156db0224724806b20110c0d34b07c
> >
> > Out of those 4, the last ("separate child and...") seems actually less
> > intrusive than the previous one. If you revert only the first three of
> > this list, does it still happen?
> >
> > Does it still happen if you unset CONFIG_CC_OPTIMIZE_FOR_SIZE and do
> > CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE instead?
>
> Oh, and it looks like 84b2789d6115 actually got some bits that shouldn't
> have been there!
>
> Assuming it does *not* work with just the first three patches reverted,
> does it work again if you revert the first three patches, and only this
> bit of the fourth?
[snip]
And as yet another experiment in this area, does it work again if you
apply this patch?
https://patchwork.ozlabs.org/project/linux-um/patch/20210303155523.124277-11-benjamin@sipsolutions.net/
Not sure it applies as-is, but you can see the schema there.
johannes
_______________________________________________
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 19:28 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
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 [this message]
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=17bc19ae635b61d50627fd1601b0ab12b5128999.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=anton.ivanov@cambridgegreys.com \
--cc=jdike@addtoit.com \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
--cc=subashab@codeaurora.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;
as well as URLs for NNTP newsgroup(s).