From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: tj@kernel.org, ast@kernel.org, john.fastabend@gmail.com,
mark.rutland@arm.com, richard@nod.at, sp3485@columbia.edu,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/3] Fix for BPF devmap percpu allocation splat
Date: Thu, 19 Oct 2017 13:14:46 +0100 (WEST) [thread overview]
Message-ID: <20171019.131446.1318832753285984633.davem@davemloft.net> (raw)
In-Reply-To: <cover.1508251210.git.daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Tue, 17 Oct 2017 16:55:51 +0200
> The set fixes a splat in devmap percpu allocation when we alloc
> the flush bitmap. Patch 1 is a prerequisite for the fix in patch 2,
> patch 1 is rather small, so if this could be routed via -net, for
> example, with Tejun's Ack that would be good. Patch 3 gets rid of
> remaining PCPU_MIN_UNIT_SIZE checks, which are percpu allocator
> internals and should not be used.
Series applied.
prev parent reply other threads:[~2017-10-19 12:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 14:55 [PATCH net 0/3] Fix for BPF devmap percpu allocation splat Daniel Borkmann
2017-10-17 14:55 ` [PATCH net 1/3] mm, percpu: add support for __GFP_NOWARN flag Daniel Borkmann
2017-10-17 15:53 ` Alexei Starovoitov
2017-10-17 14:55 ` [PATCH net 2/3] bpf: fix splat for illegal devmap percpu allocation Daniel Borkmann
2017-10-17 15:54 ` Alexei Starovoitov
2017-10-17 16:28 ` John Fastabend
2017-10-17 14:55 ` [PATCH net 3/3] bpf: do not test for PCPU_MIN_UNIT_SIZE before percpu allocations Daniel Borkmann
2017-10-17 15:55 ` Alexei Starovoitov
2017-10-17 16:29 ` John Fastabend
2017-10-17 15:03 ` [PATCH net 0/3] Fix for BPF devmap percpu allocation splat David Laight
2017-10-17 15:11 ` Daniel Borkmann
2017-10-18 13:25 ` Tejun Heo
2017-10-18 14:03 ` Daniel Borkmann
2017-10-18 14:22 ` Daniel Borkmann
2017-10-18 15:28 ` Alexei Starovoitov
2017-10-18 15:31 ` Daniel Borkmann
2017-10-18 21:45 ` Dennis Zhou
2017-10-21 16:00 ` Tejun Heo
2017-10-19 12:14 ` David Miller [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=20171019.131446.1318832753285984633.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=richard@nod.at \
--cc=sp3485@columbia.edu \
--cc=tj@kernel.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).