From: syzbot <syzbot+a568bbab323b96631e61@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, coreteam@netfilter.org,
davem@davemloft.net, fw@strlen.de, kadlec@netfilter.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
w@1wt.eu
Subject: Re: [syzbot] WARNING: kmalloc bug in hash_ipport_create
Date: Thu, 09 Sep 2021 03:32:11 -0700 [thread overview]
Message-ID: <000000000000f2bcea05cb8d8266@google.com> (raw)
In-Reply-To: <0000000000006173bf05cb892427@google.com>
syzbot has bisected this issue to:
commit 7661809d493b426e979f39ab512e3adf41fbcc69
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Wed Jul 14 16:45:49 2021 +0000
mm: don't allow oversized kvmalloc() calls
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15bb0a93300000
start commit: 626bf91a292e Merge tag 'net-5.15-rc1' of git://git.kernel...
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=17bb0a93300000
console output: https://syzkaller.appspot.com/x/log.txt?x=13bb0a93300000
kernel config: https://syzkaller.appspot.com/x/.config?x=16e23f04679ec35e
dashboard link: https://syzkaller.appspot.com/bug?extid=a568bbab323b96631e61
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=178b5d0d300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16fad1dd300000
Reported-by: syzbot+a568bbab323b96631e61@syzkaller.appspotmail.com
Fixes: 7661809d493b ("mm: don't allow oversized kvmalloc() calls")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-09-09 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 5:19 [syzbot] WARNING: kmalloc bug in hash_ipport_create syzbot
2021-09-09 10:32 ` 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=000000000000f2bcea05cb8d8266@google.com \
--to=syzbot+a568bbab323b96631e61@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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).