[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231207222755.3920286-1-andrii@kernel.org>
Date: Thu, 7 Dec 2023 14:27:52 -0800
From: Andrii Nakryiko <andrii@...nel.org>
To: <bpf@...r.kernel.org>, <netdev@...r.kernel.org>, <paul@...l-moore.com>,
<brauner@...nel.org>
CC: <linux-fsdevel@...r.kernel.org>, <linux-security-module@...r.kernel.org>,
<keescook@...omium.org>, <kernel-team@...a.com>, <sargun@...gun.me>
Subject: [PATCH RFC bpf-next 0/3] BPF FS mount options parsing follow ups
Original BPF token patch set ([0]) added delegate_xxx mount options which
supported only special "any" value and hexadecimal bitmask. This patch set
attempts to make specifying and inspecting these mount options more
human-friendly by supporting string constants matching corresponding bpf_cmd,
bpf_map_type, bpf_prog_type, and bpf_attach_type enumerators.
This is an RFC patch set and I've only converted bpf_cmd enum to be generated
through reusable mapper macro. If the consensus is that this approach is the
way to go, adding similar support for three remaining enums is just a matter
of mundane mechanical conversion in UAPI header. Kernel-side logic for all
delegate_xxx mount options is completely generic already as implemented in
patch #1.
[0] https://patchwork.kernel.org/project/netdevbpf/list/?series=805707&state=*
Andrii Nakryiko (3):
bpf: add mapper macro for bpf_cmd enum
bpf: extend parsing logic for BPF FS delegate_cmds mount option
selftests/bpf: utilize string values for delegate_xxx mount options
include/uapi/linux/bpf.h | 81 +++++------
kernel/bpf/inode.c | 127 +++++++++++++-----
tools/include/uapi/linux/bpf.h | 81 +++++------
.../testing/selftests/bpf/prog_tests/token.c | 43 +++---
4 files changed, 208 insertions(+), 124 deletions(-)
--
2.34.1
Powered by blists - more mailing lists