On Thursday, June 30, 2016 at 8:46:02 AM UTC-5, dvyukov wrote: > Currently GPF messages with KASAN look as follows: > kasan: GPF could be caused by NULL-ptr deref or user memory accessgeneral protection fault: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN > Add newlines. > > Signed-off-by: Dmitry Vyukov <dvyukov@xxxxxxxxxx> > --- > arch/x86/mm/kasan_init_64.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/x86/mm/kasan_init_64.c b/arch/x86/mm/kasan_init_64.c > index 1b1110f..0493c17 100644 > --- a/arch/x86/mm/kasan_init_64.c > +++ b/arch/x86/mm/kasan_init_64.c > @@ -54,8 +54,8 @@ static int kasan_die_handler(struct notifier_block *self, > void *data) > { > if (val == DIE_GPF) { > - pr_emerg("CONFIG_KASAN_INLINE enabled"); > - pr_emerg("GPF could be caused by NULL-ptr deref or user memory access"); > + pr_emerg("CONFIG_KASAN_INLINE enabled\n"); > + pr_emerg("GPF could be caused by NULL-ptr deref or user memory access\n"); > } > return NOTIFY_OK; > } > -- > 2.8.0.rc3.226.g39d4020