From: syzbot <syzbot+a13e5ead792d6df37818@syzkaller.appspotmail.com>
To: ast@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: KASAN: use-after-free Read in trailing_symlink
Date: Sun, 24 Mar 2019 13:44:01 -0700 [thread overview]
Message-ID: <000000000000d83e790584dd2500@google.com> (raw)
In-Reply-To: <0000000000006c6fee057bbd0ef3@google.com>
syzbot has bisected this bug to:
commit 0f98621bef5d2b7ad41f6595899660af344f5016
Author: Daniel Borkmann <daniel@iogearbox.net>
Date: Sat Oct 29 00:30:46 2016 +0000
bpf, inode: add support for symlinks and fix mtime/ctime
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1050253b200000
start commit: ef78e5ec ia64: export node_distance function
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1250253b200000
console output: https://syzkaller.appspot.com/x/log.txt?x=1450253b200000
kernel config: https://syzkaller.appspot.com/x/.config?x=c94f9f0c0363db4b
dashboard link: https://syzkaller.appspot.com/bug?extid=a13e5ead792d6df37818
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13633e47400000
Reported-by: syzbot+a13e5ead792d6df37818@syzkaller.appspotmail.com
Fixes: 0f98621bef5d ("bpf, inode: add support for symlinks and fix
mtime/ctime")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-03-24 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 17:40 KASAN: use-after-free Read in trailing_symlink syzbot
2019-03-24 20:44 ` syzbot [this message]
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=000000000000d83e790584dd2500@google.com \
--to=syzbot+a13e5ead792d6df37818@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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.