From: syzbot <syzbot+cecf5b7071a0dfb76530@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, hawk@kernel.org,
jiri@nvidia.com, john.fastabend@gmail.com, kafai@fb.com,
kpsingh@kernel.org, kuba@kernel.org, leonro@nvidia.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org, yhs@fb.com
Subject: Re: [syzbot] WARNING: kmalloc bug in bpf
Date: Fri, 22 Apr 2022 11:53:10 -0700 [thread overview]
Message-ID: <000000000000ec946105dd42bcd6@google.com> (raw)
In-Reply-To: <00000000000033acbf05d1a969aa@google.com>
syzbot suspects this issue was fixed by commit:
commit 0708a0afe291bdfe1386d74d5ec1f0c27e8b9168
Author: Daniel Borkmann <daniel@iogearbox.net>
Date: Fri Mar 4 14:26:32 2022 +0000
mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1499c6fcf00000
start commit: 1d5a47424040 sfc: The RX page_ring is optional
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=1a86c22260afac2f
dashboard link: https://syzkaller.appspot.com/bug?extid=cecf5b7071a0dfb76530
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=176738e7b00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13b4508db00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mm: Consider __GFP_NOWARN flag for oversized kvmalloc() calls
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-04-22 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 4:20 [syzbot] WARNING: kmalloc bug in bpf syzbot
2021-12-11 22:33 ` syzbot
2021-12-13 2:46 ` syzbot
2022-04-22 18:53 ` syzbot [this message]
2022-04-23 12:13 ` Dmitry Vyukov
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=000000000000ec946105dd42bcd6@google.com \
--to=syzbot+cecf5b7071a0dfb76530@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=jiri@nvidia.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=yhs@fb.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.