From: Martin KaFai Lau <kafai@fb.com>
To: <bpf@vger.kernel.org>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>, <kernel-team@fb.com>,
<netdev@vger.kernel.org>
Subject: [PATCH bpf-next 0/3] bpf: Allow inner map with different max_entries
Date: Thu, 21 May 2020 12:17:52 -0700 [thread overview]
Message-ID: <20200521191752.3448223-1-kafai@fb.com> (raw)
This series allows the outer map to be updated with inner map in different
size as long as it is safe (meaning the max_entries is not used in the
verification time during prog load).
Please see individual patch for details.
Martin KaFai Lau (3):
bpf: Clean up inner map type check
bpf: Relax the max_entries check for inner map
bpf: selftests: Add test for different inner map size
include/linux/bpf.h | 18 +++++-
include/linux/bpf_types.h | 64 +++++++++++--------
kernel/bpf/btf.c | 2 +-
kernel/bpf/map_in_map.c | 12 ++--
kernel/bpf/syscall.c | 19 +++++-
kernel/bpf/verifier.c | 2 +-
.../selftests/bpf/prog_tests/btf_map_in_map.c | 12 ++++
.../selftests/bpf/progs/test_btf_map_in_map.c | 31 +++++++++
8 files changed, 119 insertions(+), 41 deletions(-)
--
2.24.1
next reply other threads:[~2020-05-21 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 19:17 Martin KaFai Lau [this message]
2020-05-21 19:17 ` [PATCH bpf-next 1/3] bpf: Clean up inner map type check Martin KaFai Lau
2020-05-21 19:18 ` [PATCH bpf-next 2/3] bpf: Relax the max_entries check for inner map Martin KaFai Lau
2020-05-21 19:18 ` [PATCH bpf-next 3/3] bpf: selftests: Add test for different inner map size Martin KaFai Lau
2020-05-21 22:39 ` [PATCH bpf-next 0/3] bpf: Allow inner map with different max_entries Andrii Nakryiko
2020-05-21 22:59 ` Martin KaFai Lau
2020-05-21 23:10 ` Andrii Nakryiko
2020-05-21 23:16 ` Alexei Starovoitov
2020-05-22 0:06 ` Martin KaFai Lau
2020-05-26 17:47 ` Andrii Nakryiko
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=20200521191752.3448223-1-kafai@fb.com \
--to=kafai@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.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).