From: syzbot <syzbot+19e6dd9943972fa1c58a@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, axelrasmussen@google.com,
davem@davemloft.net, dsahern@kernel.org,
gregkh@linuxfoundation.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, liuhangbin@gmail.com,
netdev@vger.kernel.org, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com, tj@kernel.org, vbabka@suse.cz
Subject: Re: KASAN: use-after-free Write in kernfs_path_from_node_locked
Date: Mon, 30 Nov 2020 05:08:12 -0800 [thread overview]
Message-ID: <000000000000d0f2fb05b552b3f3@google.com> (raw)
In-Reply-To: <000000000000b8a70905b54ef5ca@google.com>
syzbot has bisected this issue to:
commit 0f818c4bc1f3dc0d6d0ea916e0ab30cf5e75f4c0
Author: Axel Rasmussen <axelrasmussen@google.com>
Date: Tue Nov 24 05:37:42 2020 +0000
mm: mmap_lock: add tracepoints around lock acquisition
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1626291d500000
start commit: 6174f052 Add linux-next specific files for 20201127
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1526291d500000
console output: https://syzkaller.appspot.com/x/log.txt?x=1126291d500000
kernel config: https://syzkaller.appspot.com/x/.config?x=79c69cf2521bef9c
dashboard link: https://syzkaller.appspot.com/bug?extid=19e6dd9943972fa1c58a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12c3351d500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c28809500000
Reported-by: syzbot+19e6dd9943972fa1c58a@syzkaller.appspotmail.com
Fixes: 0f818c4bc1f3 ("mm: mmap_lock: add tracepoints around lock acquisition")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-11-30 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 8:40 KASAN: use-after-free Write in kernfs_path_from_node_locked syzbot
2020-11-30 13:08 ` syzbot [this message]
2020-11-30 18:02 ` Axel Rasmussen
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=000000000000d0f2fb05b552b3f3@google.com \
--to=syzbot+19e6dd9943972fa1c58a@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
--cc=vbabka@suse.cz \
/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.