[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d87d7844-5dce-b423-9d54-4e51d482ba5f@i-love.sakura.ne.jp>
Date: Wed, 17 Jul 2019 19:13:52 +0900
From: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: syzbot <syzbot+f5ceb7c55f59455035ca@...kaller.appspotmail.com>,
ast@...nel.org, daniel@...earbox.net, john.fastabend@...il.com,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: KASAN: use-after-free Write in check_noncircular
This is not a TOMOYO's bug. But
On 2019/07/17 17:58, syzbot wrote:
> ==================================================================
> BUG: KASAN: use-after-free in check_noncircular+0x91/0x560 kernel/locking/lockdep.c:1722
> Write of size 56 at addr ffff888089815160 by task syz-executor.4/8772
>
> CPU: 1 PID: 8772 Comm: syz-executor.4 Not tainted 5.2.0+ #31
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
> Call Trace:
>
what happened here? No trace was printed to console output?
> Allocated by task 8457:
Powered by blists - more mailing lists