From: syzbot <syzbot+df0d0f5895ef1f41a65b@syzkaller.appspotmail.com>
To: allison@lohutok.net, arvid.brodin@alten.se,
coreteam@netfilter.org, davem@davemloft.net, fw@strlen.de,
info@metux.net, jeremy@azazel.net, kadlec@netfilter.org,
kstewart@linuxfoundation.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pablo@netfilter.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, xiyou.wangcong@gmail.com
Subject: Re: KASAN: slab-out-of-bounds Read in bitmap_ip_gc
Date: Sat, 18 Jan 2020 20:41:01 -0800 [thread overview]
Message-ID: <00000000000027c814059c76c818@google.com> (raw)
In-Reply-To: <000000000000717523059c6cabc9@google.com>
syzbot has bisected this bug to:
commit b9a1e627405d68d475a3c1f35e685ccfb5bbe668
Author: Cong Wang <xiyou.wangcong@gmail.com>
Date: Thu Jul 4 00:21:13 2019 +0000
hsr: implement dellink to clean up resources
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13ddfa85e00000
start commit: 25e73aad Merge tag 'io_uring-5.5-2020-01-16' of git://git...
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=103dfa85e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=17ddfa85e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=cfbb8fa33f49f9f3
dashboard link: https://syzkaller.appspot.com/bug?extid=df0d0f5895ef1f41a65b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=124774c9e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15aa48d6e00000
Reported-by: syzbot+df0d0f5895ef1f41a65b@syzkaller.appspotmail.com
Fixes: b9a1e627405d ("hsr: implement dellink to clean up resources")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-01-19 4:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 16:37 KASAN: slab-out-of-bounds Read in bitmap_ip_gc syzbot
2020-01-19 4:41 ` 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=00000000000027c814059c76c818@google.com \
--to=syzbot+df0d0f5895ef1f41a65b@syzkaller.appspotmail.com \
--cc=allison@lohutok.net \
--cc=arvid.brodin@alten.se \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=info@metux.net \
--cc=jeremy@azazel.net \
--cc=kadlec@netfilter.org \
--cc=kstewart@linuxfoundation.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=tglx@linutronix.de \
--cc=xiyou.wangcong@gmail.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 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).