From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Petr Mladek <pmladek@suse.com>,
kernel test robot <shun.hao@intel.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Dave Hansen <dave.hansen@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jan Kara <jack@suse.cz>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Byungchul Park <byungchul.park@lge.com>,
Tejun Heo <tj@kernel.org>, Pavel Machek <pavel@ucw.cz>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>,
kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: [lkp-robot] [printk] c162d5b433: BUG:KASAN:use-after-scope_in_c
Date: Fri, 2 Mar 2018 00:19:34 +0900 [thread overview]
Message-ID: <20180301151934.GA507@tigerII.localdomain> (raw)
In-Reply-To: <CACT4Y+ZUDu588gwgCbqru5D1RD5C+s3+E5ydhP7h9RoCjwQWJw@mail.gmail.com>
On (03/01/18 09:51), Dmitry Vyukov wrote:
> > https://marc.info/?l=linux-kernel&m=151200883525299
> >
> > [..]
> >> I feel lost a bit.
> >
> > Yeah... can't understand what's going on there.
> >
> > The last time kasan didn't like this part
> >
> > [ 0.003333] ? console_unlock+0x605/0xcc0:
> > atomic_read at arch/x86/include/asm/atomic.h:27
> > (inlined by) static_key_count at include/linux/jump_label.h:191
> > (inlined by) static_key_false at include/linux/jump_label.h:201
> > (inlined by) trace_console_rcuidle at include/trace/events/printk.h:10
> > (inlined by) call_console_drivers at kernel/printk/printk.c:1556
> > (inlined by) console_unlock at kernel/printk/printk.c:2233
> >
> > complaining that there was a write of size 4... at atomic_read().
>
> Hi Sergey,
>
> Where is that report?
> I doubt that KASAN has instrumented a read as a write (at least there
> are no such known cases), so perhaps it's pointing to some other
> memory access.
Hello Dmitry,
I believe it's this one
https://marc.info/?l=linux-kernel&m=151200883525299
-ss
next prev parent reply other threads:[~2018-03-01 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 5:34 [lkp-robot] [printk] c162d5b433: BUG:KASAN:use-after-scope_in_c kernel test robot
2018-02-28 10:23 ` Petr Mladek
2018-02-28 15:59 ` Petr Mladek
2018-03-01 1:37 ` Sergey Senozhatsky
2018-03-01 8:47 ` Dmitry Vyukov
2018-03-01 10:06 ` Tetsuo Handa
2018-03-01 14:09 ` Dmitry Vyukov
2018-03-01 14:14 ` Ard Biesheuvel
2018-03-01 16:38 ` Kees Cook
2018-03-02 3:48 ` Hao, Shun
2018-03-01 8:51 ` Dmitry Vyukov
2018-03-01 15:19 ` Sergey Senozhatsky [this message]
2018-03-01 15:53 ` Dmitry Vyukov
2018-03-02 5:10 ` 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=20180301151934.GA507@tigerII.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=byungchul.park@lge.com \
--cc=dave.hansen@intel.com \
--cc=dvyukov@google.com \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=pavel@ucw.cz \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=shun.hao@intel.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=xiyou.wangcong@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