lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 15 Nov 2016 11:19:03 +0100 From: Ingo Molnar <mingo@...nel.org> To: Borislav Petkov <bp@...en8.de> Cc: X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>, Andy Lutomirski <luto@...nel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, Peter Zijlstra <peterz@...radead.org> Subject: Re: [RFC PATCH] x86/debug: Dump more detailed segfault info * Borislav Petkov <bp@...en8.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
Powered by blists - more mailing lists