From: syzbot <syzbot+b96275fd6ad891076ced@syzkaller.appspotmail.com>
To: arvid.brodin@alten.se, coreteam@netfilter.org,
davem@davemloft.net, florent.fourcot@wifirst.fr, fw@strlen.de,
jeremy@azazel.net, johannes.berg@intel.com, kadlec@netfilter.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
syzkaller-bugs@googlegroups.com, xiyou.wangcong@gmail.com
Subject: Re: KASAN: slab-out-of-bounds Read in bitmap_port_destroy
Date: Thu, 23 Jan 2020 20:55:00 -0800 [thread overview]
Message-ID: <000000000000638fae059cdb8fe8@google.com> (raw)
In-Reply-To: <000000000000204b4d059cd6d766@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=17d0c611e00000
start commit: 131701c6 Merge tag 'leds-5.5-rc8' of git://git.kernel.org/..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=1430c611e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=1030c611e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=83c00afca9cf5153
dashboard link: https://syzkaller.appspot.com/bug?extid=b96275fd6ad891076ced
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15fba721e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1339726ee00000
Reported-by: syzbot+b96275fd6ad891076ced@syzkaller.appspotmail.com
Fixes: b9a1e627405d ("hsr: implement dellink to clean up resources")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-01-24 4:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 23:17 KASAN: slab-out-of-bounds Read in bitmap_port_destroy syzbot
2020-01-24 4:55 ` syzbot [this message]
2020-03-14 13:10 ` syzbot
[not found] <20200124085521.12504-1-hdanton@sina.com>
2020-01-24 9:11 ` Dan Carpenter
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=000000000000638fae059cdb8fe8@google.com \
--to=syzbot+b96275fd6ad891076ced@syzkaller.appspotmail.com \
--cc=arvid.brodin@alten.se \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=florent.fourcot@wifirst.fr \
--cc=fw@strlen.de \
--cc=jeremy@azazel.net \
--cc=johannes.berg@intel.com \
--cc=kadlec@netfilter.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=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).