From: syzbot <syzbot+24d0577de55b8b8f6975@syzkaller.appspotmail.com>
To: allison@lohutok.net, arvid.brodin@alten.se,
coreteam@netfilter.org, davem@davemloft.net,
dirk.vandermerwe@netronome.com, fw@strlen.de,
gregkh@linuxfoundation.org, jakub.kicinski@netronome.com,
jeremy@azazel.net, kadlec@netfilter.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
Subject: Re: KASAN: slab-out-of-bounds Write in bitmap_ip_del
Date: Mon, 20 Jan 2020 05:00:01 -0800 [thread overview]
Message-ID: <0000000000008916f1059c91de99@google.com> (raw)
In-Reply-To: <000000000000f649ad059c8ca893@google.com>
syzbot has bisected this bug to:
commit 0f93242d96ff5a04fe02c4978e8dddb014235971
Author: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Tue Jul 9 02:53:08 2019 +0000
nfp: tls: ignore queue limits for delete commands
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11f4e966e00000
start commit: 09d4f10a net: sched: act_ctinfo: fix memory leak
git tree: net
final crash: https://syzkaller.appspot.com/x/report.txt?x=13f4e966e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=15f4e966e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e89bd00623fe71e
dashboard link: https://syzkaller.appspot.com/bug?extid=24d0577de55b8b8f6975
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1799c135e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=176b8faee00000
Reported-by: syzbot+24d0577de55b8b8f6975@syzkaller.appspotmail.com
Fixes: 0f93242d96ff ("nfp: tls: ignore queue limits for delete commands")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-01-20 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 6:47 KASAN: slab-out-of-bounds Write in bitmap_ip_del syzbot
2020-01-20 13:00 ` syzbot [this message]
2020-02-21 19:05 ` syzbot
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=0000000000008916f1059c91de99@google.com \
--to=syzbot+24d0577de55b8b8f6975@syzkaller.appspotmail.com \
--cc=allison@lohutok.net \
--cc=arvid.brodin@alten.se \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dirk.vandermerwe@netronome.com \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=jakub.kicinski@netronome.com \
--cc=jeremy@azazel.net \
--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=tglx@linutronix.de \
/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.