From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC PATCH] x86/debug: Dump more detailed segfault info
Date: Tue, 15 Nov 2016 11:19:03 +0100 [thread overview]
Message-ID: <20161115101903.GA15249@gmail.com> (raw)
In-Reply-To: <20161115100655.flju5ce3zxtrcyx4@pd.tnic>
* Borislav Petkov <bp@alien8.de> wrote:
> On Tue, Nov 15, 2016 at 07:14:47AM +0100, Ingo Molnar wrote:
> > So I think the line breaking artifact might be due to the following commit:
> >
> > bfd8d3f23b51 ("printk: make reading the kernel log flush pending lines")
> >
> > ... which Linus reverted upstream a few hours ago:
>
> Probably. I guess this doesn't happen when running my guest here because
> I have the segfault logging change ontop of -rc4.
Well, bfd8d3f23b51 was part of -rc1 already, so you have it too.
What might have made the difference is that I tested it on real hardware with
serial logging, which delays printk() and might have created the race with the
systemd kernel logger. (Which is impossible to turn off :-( )
Thanks,
Ingo
next prev parent reply other threads:[~2016-11-15 10:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 10:19 [RFC PATCH] x86/debug: Dump more detailed segfault info Borislav Petkov
2016-11-12 11:06 ` Ingo Molnar
2016-11-12 12:27 ` Borislav Petkov
2016-11-13 7:39 ` Ingo Molnar
2016-11-13 11:25 ` Borislav Petkov
2016-11-13 15:49 ` Borislav Petkov
2016-11-15 6:14 ` Ingo Molnar
2016-11-15 10:06 ` Borislav Petkov
2016-11-15 10:19 ` Ingo Molnar [this message]
2016-11-15 10:22 ` Borislav Petkov
2016-11-15 10:38 ` Ingo Molnar
2016-11-13 16:15 ` Andy Lutomirski
2016-11-14 6:18 ` Borislav Petkov
2016-11-17 23:33 ` Andy Lutomirski
2016-11-18 12:38 ` Borislav Petkov
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=20161115101903.GA15249@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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).