From: syzbot <syzbot+eaeb616d85c9a0afec7d@syzkaller.appspotmail.com>
To: cmetcalf@ezchip.com, coreteam@netfilter.org, davem@davemloft.net,
dvyukov@google.com, gang.chen.5i5j@gmail.com, kaber@trash.net,
kadlec@blackhole.kfki.hu, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: KASAN: use-after-free Read in blkdev_get
Date: Sun, 24 Nov 2019 11:07:00 -0800 [thread overview]
Message-ID: <0000000000000beff305981c5ac6@google.com> (raw)
In-Reply-To: <000000000000e59aab056e8873ae@google.com>
syzbot has bisected this bug to:
commit 77ef8f5177599efd0cedeb52c1950c1bd73fa5e3
Author: Chris Metcalf <cmetcalf@ezchip.com>
Date: Mon Jan 25 20:05:34 2016 +0000
tile kgdb: fix bug in copy to gdb regs, and optimize memset
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1131bc0ee00000
start commit: f5b7769e Revert "debugfs: inode: debugfs_create_dir uses m..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1331bc0ee00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1531bc0ee00000
kernel config: https://syzkaller.appspot.com/x/.config?x=709f8187af941e84
dashboard link: https://syzkaller.appspot.com/bug?extid=eaeb616d85c9a0afec7d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=177f898f800000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=147eb85f800000
Reported-by: syzbot+eaeb616d85c9a0afec7d@syzkaller.appspotmail.com
Fixes: 77ef8f517759 ("tile kgdb: fix bug in copy to gdb regs, and optimize
memset")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-11-24 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 16:27 KASAN: use-after-free Read in blkdev_get syzbot
2018-12-05 19:50 ` Dmitry Vyukov
2019-11-24 19:07 ` syzbot [this message]
2019-11-24 19:30 ` Al Viro
2019-11-30 11:06 ` Duncan Roe
2019-11-30 15:53 ` Dmitry Vyukov
2019-12-01 0:04 ` Duncan Roe
2019-12-02 6:47 ` Dmitry Vyukov
2019-12-02 9:31 ` Duncan Roe
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=0000000000000beff305981c5ac6@google.com \
--to=syzbot+eaeb616d85c9a0afec7d@syzkaller.appspotmail.com \
--cc=cmetcalf@ezchip.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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.