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, 12 Jul 2016 16:32:26 +0200 From: Vegard Nossum <vegard.nossum@...cle.com> To: Andrey Ryabinin <aryabinin@...tuozzo.com>, Ingo Molnar <mingo@...nel.org> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH] kasan: use \n with pr_emerg On 07/12/2016 04:27 PM, Andrey Ryabinin wrote: > On 07/12/2016 05:16 PM, Vegard Nossum wrote: >> We really ought to be using \n with pr_*() so the 'general protection >> fault...' starts on a line of its own. With this patch it looks better: >> >> kasan: CONFIG_KASAN_INLINE enabled >> kasan: GPF could be caused by NULL-ptr deref or user memory access >> general protection fault: 0000 [#1] KASAN >> CPU: 0 PID: 56 Comm: ext4.exe Not tainted 4.7.0-rc7+ #650 >> > > Dmitry fixed that already: http://lkml.kernel.org/g/<1467294357-98002-1-git-send-email-dvyukov@...gle.com> > Great, thanks :-) Vegard
Powered by blists - more mailing lists