From: lukefrierson888@gmail.com
To: kasan-dev <kasan-dev@googlegroups.com>
Cc: akpm@linux-foundation.org, ryabinin.a.a@gmail.com,
glider@google.com, linux-mm@kvack.org, dvyukov@google.com
Subject: Re: [PATCH] kasan: add newline to messages
Date: Mon, 30 Jan 2017 01:58:37 -0800 (PST) [thread overview]
Message-ID: <09708a3e-ef88-4695-8f3e-2cb69210b9ca@googlegroups.com> (raw)
In-Reply-To: <1467294357-98002-1-git-send-email-dvyukov@google.com>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
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@google.com>
> ---
> 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
prev parent reply other threads:[~2017-01-30 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 13:45 Dmitry Vyukov
2016-06-30 13:48 ` Andrey Ryabinin
2016-08-31 2:07 ` amanda4ray
2016-09-08 0:03 ` bethelpchalfant
2017-01-30 9:58 ` lukefrierson888 [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=09708a3e-ef88-4695-8f3e-2cb69210b9ca@googlegroups.com \
--to=lukefrierson888@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=ryabinin.a.a@gmail.com \
/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