From: Michal Hocko <mhocko@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: syzbot <syzbot+1a240cdb1f4cc88819df@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, dhowells@redhat.com,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mingo@kernel.org, rppt@linux.vnet.ibm.com,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz,
viro@zeniv.linux.org.uk, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org
Subject: Re: WARNING in kvmalloc_node
Date: Wed, 14 Feb 2018 09:43:08 +0100 [thread overview]
Message-ID: <20180214084308.GX3443@dhcp22.suse.cz> (raw)
In-Reply-To: <20180214025533.GA28811@bombadil.infradead.org>
On Tue 13-02-18 18:55:33, Matthew Wilcox wrote:
> On Tue, Feb 13, 2018 at 03:59:01PM -0800, syzbot wrote:
[...]
> > kvmalloc include/linux/mm.h:541 [inline]
> > kvmalloc_array include/linux/mm.h:557 [inline]
> > __ptr_ring_init_queue_alloc include/linux/ptr_ring.h:474 [inline]
> > ptr_ring_init include/linux/ptr_ring.h:492 [inline]
> > __cpu_map_entry_alloc kernel/bpf/cpumap.c:359 [inline]
> > cpu_map_update_elem+0x3c3/0x8e0 kernel/bpf/cpumap.c:490
> > map_update_elem kernel/bpf/syscall.c:698 [inline]
>
> Blame the BPF people, not the MM people ;-)
Yes. kvmalloc (the vmalloc part) doesn't support GFP_ATOMIC semantic.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-14 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 23:59 WARNING in kvmalloc_node syzbot
2018-02-14 2:55 ` Matthew Wilcox
2018-02-14 8:43 ` Michal Hocko [this message]
2018-02-14 9:28 ` Daniel Borkmann
2018-02-14 11:47 ` Jason Wang
2018-02-14 11:51 ` Michal Hocko
2018-02-14 12:02 ` Jason Wang
2018-02-14 12:17 ` Daniel Borkmann
2018-02-14 12:29 ` Jesper Dangaard Brouer
2018-02-14 12:47 ` Jason Wang
2018-02-14 13:29 ` Daniel Borkmann
2018-02-14 19:20 ` 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=20180214084308.GX3443@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dhowells@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=syzbot+1a240cdb1f4cc88819df@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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).