From: syzbot <syzbot+d2a8670576fa63d18623@syzkaller.appspotmail.com>
To: 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_nl_node_dump_monitor_peer
Date: Wed, 09 Oct 2019 02:22:00 -0700 [thread overview]
Message-ID: <0000000000003bdc5f059476d153@google.com> (raw)
In-Reply-To: <0000000000003dc9ba059475614f@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=14ac08e7600000
start commit: f9867b51 netdevsim: fix spelling mistake "forbidded" -> "f..
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=16ac08e7600000
console output: https://syzkaller.appspot.com/x/log.txt?x=12ac08e7600000
kernel config: https://syzkaller.appspot.com/x/.config?x=d9be300620399522
dashboard link: https://syzkaller.appspot.com/bug?extid=d2a8670576fa63d18623
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16d3e04f600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13a76593600000
Reported-by: syzbot+d2a8670576fa63d18623@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
next prev parent reply other threads:[~2019-10-09 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 7:39 KASAN: use-after-free Read in tipc_nl_node_dump_monitor_peer syzbot
2019-10-09 9:22 ` syzbot [this message]
2019-10-09 9:45 ` Jiri Pirko
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=0000000000003bdc5f059476d153@google.com \
--to=syzbot+d2a8670576fa63d18623@syzkaller.appspotmail.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 \
--cc=ying.xue@windriver.com \
/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.