From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>
Cc: 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 16:07:30 +0300 [thread overview]
Message-ID: <ecd089a9-5ec4-c512-aa37-7e0d59b64894@virtuozzo.com> (raw)
In-Reply-To: <20171130082909.GA469@jagdpanzerIV>
On 11/30/2017 11:29 AM, Sergey Senozhatsky wrote:
> 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.
.config has CONFIG_GCC_PLUGIN_STRUCTLEAK_BYREF_ALL=y
It's known to cause use-after-scope problems, so printk/console code is likely
has nothing to do with the bug.
>>
>> 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).
I suspect you don't have gcc 7. That's is requirement for use-after-scope.
> -ss
>
next prev parent reply other threads:[~2017-11-30 13:04 UTC|newest]
Thread overview: 10+ 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 6:47 ` Sergey Senozhatsky
2017-11-30 8:16 ` Dmitry Vyukov
2017-11-30 8:29 ` Sergey Senozhatsky
2017-11-30 9:05 ` Fengguang Wu
2017-11-30 13:07 ` Andrey Ryabinin [this message]
2017-12-01 1:58 ` Sergey Senozhatsky
2017-11-30 14:30 ` Fengguang Wu
2017-11-30 14:45 ` Dmitry Vyukov
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=ecd089a9-5ec4-c512-aa37-7e0d59b64894@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=aleksey.makarov@linaro.org \
--cc=dvyukov@google.com \
--cc=fengguang.wu@intel.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mingo@kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=nikitas.angelinas@gmail.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).