All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum@oracle.com>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>,
	Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kasan: use \n with pr_emerg
Date: Tue, 12 Jul 2016 16:32:26 +0200	[thread overview]
Message-ID: <5784FF7A.7050702@oracle.com> (raw)
In-Reply-To: <5784FE4E.3000404@virtuozzo.com>

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@google.com>
>

Great, thanks :-)


Vegard

      reply	other threads:[~2016-07-12 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12 14:16 [PATCH] kasan: use \n with pr_emerg Vegard Nossum
2016-07-12 14:27 ` Andrey Ryabinin
2016-07-12 14:32   ` Vegard Nossum [this message]

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=5784FF7A.7050702@oracle.com \
    --to=vegard.nossum@oracle.com \
    --cc=aryabinin@virtuozzo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.