From: syzbot <syzbot+fb731ca573367b7f6564@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 link_path_walk
Date: Sun, 24 Mar 2019 21:52:01 -0700 [thread overview]
Message-ID: <000000000000143bcd0584e3f7ea@google.com> (raw)
In-Reply-To: <000000000000663620057bbd0e9d@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=13c347a3200000
start commit: ef78e5ec ia64: export node_distance function
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=102347a3200000
console output: https://syzkaller.appspot.com/x/log.txt?x=17c347a3200000
kernel config: https://syzkaller.appspot.com/x/.config?x=c94f9f0c0363db4b
dashboard link: https://syzkaller.appspot.com/bug?extid=fb731ca573367b7f6564
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11116225400000
Reported-by: syzbot+fb731ca573367b7f6564@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
next prev parent reply other threads:[~2019-03-25 4:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 17:40 KASAN: use-after-free Read in link_path_walk syzbot
2019-03-25 4:52 ` syzbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-24 3:45 Dae R. Jeong
2018-07-24 4:08 ` DaeRyong Jeong
2018-07-24 5:17 ` Al Viro
2018-07-24 5:29 ` Al Viro
2018-08-06 13:01 ` Al Viro
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=000000000000143bcd0584e3f7ea@google.com \
--to=syzbot+fb731ca573367b7f6564@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).