From: syzbot <syzbot+cd43695a64bcd21b8596@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, coreteam@netfilter.org,
davem@davemloft.net, eric.dumazet@gmail.com, 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 nf_tables_newset
Date: Sun, 05 Sep 2021 22:25:07 -0700 [thread overview]
Message-ID: <000000000000486b8b05cb4cdf5c@google.com> (raw)
In-Reply-To: <000000000000ed8c0a05cb1ff6d8@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=15f767b1300000
start commit: a9c9a6f741cd Merge tag 'scsi-misc' of git://git.kernel.org..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=17f767b1300000
console output: https://syzkaller.appspot.com/x/log.txt?x=13f767b1300000
kernel config: https://syzkaller.appspot.com/x/.config?x=7860a0536ececf0c
dashboard link: https://syzkaller.appspot.com/bug?extid=cd43695a64bcd21b8596
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13281b33300000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1077b4b9300000
Reported-by: syzbot+cd43695a64bcd21b8596@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-06 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 23:50 [syzbot] WARNING: kmalloc bug in nf_tables_newset syzbot
2021-09-03 23:56 ` Eric Dumazet
2021-09-06 5:25 ` 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=000000000000486b8b05cb4cdf5c@google.com \
--to=syzbot+cd43695a64bcd21b8596@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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 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.