From: syzbot <syzbot+dbe02e13bcce52bcf182@syzkaller.appspotmail.com>
To: Ying.Xue@windriver.com, davem@davemloft.net, jiri@mellanox.com,
jon.maloy@ericsson.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tipc-discussion@lists.sourceforge.net, ying.xue@windriver.com
Subject: Re: KASAN: use-after-free Read in tipc_udp_nl_dump_remoteip
Date: Tue, 08 Oct 2019 14:06:00 -0700 [thread overview]
Message-ID: <0000000000000f13e105946c89e9@google.com> (raw)
In-Reply-To: <000000000000c1e5e8059456a5bf@google.com>
syzbot has bisected this bug to:
commit 057af70713445fad2459aa348c9c2c4ecf7db938
Author: Jiri Pirko <jiri@mellanox.com>
Date: Sat Oct 5 18:04:39 2019 +0000
net: tipc: have genetlink code to parse the attrs during dumpit
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11675620e00000
start commit: 056ddc38 Merge branch 'stmmac-next'
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=13675620e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=15675620e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d9be300620399522
dashboard link: https://syzkaller.appspot.com/bug?extid=dbe02e13bcce52bcf182
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137ecdfb600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15dd0d0b600000
Reported-by: syzbot+dbe02e13bcce52bcf182@syzkaller.appspotmail.com
Fixes: 057af7071344 ("net: tipc: have genetlink code to parse the attrs
during dumpit")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-10-08 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 18:59 KASAN: use-after-free Read in tipc_udp_nl_dump_remoteip syzbot
2019-10-08 21:06 ` 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=0000000000000f13e105946c89e9@google.com \
--to=syzbot+dbe02e13bcce52bcf182@syzkaller.appspotmail.com \
--cc=Ying.Xue@windriver.com \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
/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).