From: syzbot <syzbot+33fc3ad6fa11675e1a7e@syzkaller.appspotmail.com>
To: a@unstable.cc, b.a.t.m.a.n@lists.open-mesh.org,
coreteam@netfilter.org, davem@davemloft.net,
florent.fourcot@wifirst.fr, fw@strlen.de, jeremy@azazel.net,
johannes.berg@intel.com, kadlec@blackhole.kfki.hu,
kadlec@netfilter.org, linux-kernel@vger.kernel.org,
mareklindner@neomailbox.ch, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
po-hsu.lin@canonical.com, skhan@linuxfoundation.org,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in bitmap_ipmac_ext_cleanup
Date: Wed, 19 Feb 2020 07:46:02 -0800 [thread overview]
Message-ID: <0000000000008a7b14059eefafff@google.com> (raw)
In-Reply-To: <000000000000c7999e059c86eebe@google.com>
syzbot suspects this bug was fixed by commit:
commit 32c72165dbd0e246e69d16a3ad348a4851afd415
Author: Kadlecsik József <kadlec@blackhole.kfki.hu>
Date: Sun Jan 19 21:06:49 2020 +0000
netfilter: ipset: use bitmap infrastructure completely
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13435a7ee00000
start commit: 8f8972a3 Merge tag 'mtd/fixes-for-5.5-rc7' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=d9290aeb7e6cf1c4
dashboard link: https://syzkaller.appspot.com/bug?extid=33fc3ad6fa11675e1a7e
userspace arch: i386
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15982cc9e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11be38d6e00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: netfilter: ipset: use bitmap infrastructure completely
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2020-02-19 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 23:57 KASAN: use-after-free Read in bitmap_ipmac_ext_cleanup syzbot
2020-01-20 23:16 ` syzbot
2020-02-19 15:46 ` 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=0000000000008a7b14059eefafff@google.com \
--to=syzbot+33fc3ad6fa11675e1a7e@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--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@blackhole.kfki.hu \
--cc=kadlec@netfilter.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=po-hsu.lin@canonical.com \
--cc=skhan@linuxfoundation.org \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.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.