From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: lkp@lists.01.org
Subject: Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0
Date: Thu, 30 Nov 2017 17:29:09 +0900 [thread overview]
Message-ID: <20171130082909.GA469@jagdpanzerIV> (raw)
In-Reply-To: <CACT4Y+amQZApke6MneeK0tax=MzDbj5bce6r4MuSf8PHpzeaoA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
On (11/30/17 09:16), Dmitry Vyukov wrote:
[..]
> > to be honest, this backtrace hardly makes any sense to me.
> >
> > vprintk_emit()
> > reserve_standard_io_resources()
> > __flush_tlb_all()
> > vprintk_emit()
> > __down_trylock_console_sem()
> > wake_up_klogd()
> > console_unlock()
> >
> > I need some help here.
>
>
> You can try dirty patch from here:
> https://groups.google.com/d/msg/kasan-dev/iDb5bhcMBT0/55QzwWaHAwAJ
> It should make KASAN print the exact variable name and frame where it
> was allocated.
would be good if Fengguang can try this out. I can't reproduce the
problem on my x86 box (linux-next and Linus's trees both work fine
for me with KASAN + lockdep + TRACE_IRQ).
-ss
WARNING: multiple messages have this Message-ID (diff)
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Fengguang Wu <fengguang.wu@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Aleksey Makarov <aleksey.makarov@linaro.org>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Nikitas Angelinas <nikitas.angelinas@gmail.com>, LKP <lkp@01.org>,
kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0
Date: Thu, 30 Nov 2017 17:29:09 +0900 [thread overview]
Message-ID: <20171130082909.GA469@jagdpanzerIV> (raw)
In-Reply-To: <CACT4Y+amQZApke6MneeK0tax=MzDbj5bce6r4MuSf8PHpzeaoA@mail.gmail.com>
On (11/30/17 09:16), Dmitry Vyukov wrote:
[..]
> > to be honest, this backtrace hardly makes any sense to me.
> >
> > vprintk_emit()
> > reserve_standard_io_resources()
> > __flush_tlb_all()
> > vprintk_emit()
> > __down_trylock_console_sem()
> > wake_up_klogd()
> > console_unlock()
> >
> > I need some help here.
>
>
> You can try dirty patch from here:
> https://groups.google.com/d/msg/kasan-dev/iDb5bhcMBT0/55QzwWaHAwAJ
> It should make KASAN print the exact variable name and frame where it
> was allocated.
would be good if Fengguang can try this out. I can't reproduce the
problem on my x86 box (linux-next and Linus's trees both work fine
for me with KASAN + lockdep + TRACE_IRQ).
-ss
next prev parent reply other threads:[~2017-11-30 8:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 2:26 [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0 Fengguang Wu
2017-11-30 2:26 ` Fengguang Wu
2017-11-30 6:47 ` Sergey Senozhatsky
2017-11-30 6:47 ` Sergey Senozhatsky
2017-11-30 8:16 ` Dmitry Vyukov
2017-11-30 8:16 ` Dmitry Vyukov
2017-11-30 8:29 ` Sergey Senozhatsky [this message]
2017-11-30 8:29 ` Sergey Senozhatsky
2017-11-30 9:05 ` Fengguang Wu
2017-11-30 9:05 ` Fengguang Wu
2017-11-30 13:07 ` Andrey Ryabinin
2017-11-30 13:07 ` Andrey Ryabinin
2017-12-01 1:58 ` Sergey Senozhatsky
2017-12-01 1:58 ` Sergey Senozhatsky
2017-11-30 14:30 ` Fengguang Wu
2017-11-30 14:30 ` Fengguang Wu
2017-11-30 14:45 ` Dmitry Vyukov
2017-11-30 14:45 ` Dmitry Vyukov
2017-12-01 1:32 ` Sergey Senozhatsky
2017-12-01 1:32 ` Sergey Senozhatsky
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=20171130082909.GA469@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=lkp@lists.01.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.