From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: "Daniel Borkmann" <daniel@iogearbox.net>,
"Willy Tarreau" <w@1wt.eu>,
syzbot <syzbot+11421fbbff99b989670e@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, "Andrii Nakryiko" <andrii@kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Björn Töpel" <bjorn.topel@intel.com>, bpf <bpf@vger.kernel.org>,
"David Miller" <davem@davemloft.net>,
fgheet255t@gmail.com, "Jesper Dangaard Brouer" <hawk@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
"Jonathan Lemon" <jonathan.lemon@gmail.com>,
"Martin KaFai Lau" <kafai@fb.com>,
"KP Singh" <kpsingh@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, "Karlsson,
Magnus" <magnus.karlsson@intel.com>,
mudongliangabcd@gmail.com, Netdev <netdev@vger.kernel.org>,
"Song Liu" <songliubraving@fb.com>,
syzkaller-bugs@googlegroups.com,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Yonghong Song" <yhs@fb.com>
Subject: Re: [syzbot] WARNING: kmalloc bug in xdp_umem_create (2)
Date: Thu, 10 Feb 2022 20:56:03 +0300 [thread overview]
Message-ID: <20220210175603.GL1951@kadam> (raw)
In-Reply-To: <20220210174507.GK1951@kadam>
On Thu, Feb 10, 2022 at 08:45:08PM +0300, Dan Carpenter wrote:
> Is it normally going to huge? You could call vmalloc() instead of
> kvmalloc().
Wait that would make the allocation succeed... We don't want that.
That was a dumb idea. Forget I said that.
regards,
dan carpenter
next prev parent reply other threads:[~2022-02-10 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 10:55 [syzbot] WARNING: kmalloc bug in xdp_umem_create (2) syzbot
2021-12-07 8:49 ` Björn Töpel
2021-12-07 9:19 ` Daniel Borkmann
2022-02-10 2:59 ` syzbot
2022-02-10 6:08 ` syzbot
2022-02-10 8:11 ` Willy Tarreau
2022-02-10 8:35 ` Daniel Borkmann
2022-02-10 16:18 ` Björn Töpel
2022-02-10 17:45 ` Dan Carpenter
2022-02-10 17:56 ` Dan Carpenter [this message]
2022-02-10 18:04 ` Linus Torvalds
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=20220210175603.GL1951@kadam \
--to=dan.carpenter@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=fgheet255t@gmail.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jonathan.lemon@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=magnus.karlsson@intel.com \
--cc=mudongliangabcd@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+11421fbbff99b989670e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
--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.