From: Yonghong Song <yhs@fb.com>
To: Stanislav Fomichev <sdf@google.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, kpsingh@kernel.org, jakub@cloudflare.com
Subject: Re: [PATCH bpf-next v7 00/11] bpf: cgroup_sock lsm flavor
Date: Thu, 19 May 2022 16:34:22 -0700 [thread overview]
Message-ID: <3a732a8d-6e4f-0154-e317-795baa64022d@fb.com> (raw)
In-Reply-To: <20220518225531.558008-1-sdf@google.com>
On 5/18/22 3:55 PM, Stanislav Fomichev wrote:
> This series implements new lsm flavor for attaching per-cgroup programs to
> existing lsm hooks. The cgroup is taken out of 'current', unless
> the first argument of the hook is 'struct socket'. In this case,
> the cgroup association is taken out of socket. The attachment
> looks like a regular per-cgroup attachment: we add new BPF_LSM_CGROUP
> attach type which, together with attach_btf_id, signals per-cgroup lsm.
> Behind the scenes, we allocate trampoline shim program and
> attach to lsm. This program looks up cgroup from current/socket
> and runs cgroup's effective prog array. The rest of the per-cgroup BPF
> stays the same: hierarchy, local storage, retval conventions
> (return 1 == success).
>
> Current limitations:
> * haven't considered sleepable bpf; can be extended later on
> * not sure the verifier does the right thing with null checks;
> see latest selftest for details
> * total of 10 (global) per-cgroup LSM attach points
>
> Cc: ast@kernel.org
> Cc: daniel@iogearbox.net
> Cc: kafai@fb.com
> Cc: kpsingh@kernel.org
> Cc: jakub@cloudflare.com
>
> v7:
> - there were a lot of comments last time, hope I didn't forget anything,
> some of the bigger ones:
> - Martin: use/extend BTF_SOCK_TYPE_SOCKET
> - Martin: expose bpf_set_retval
> - Martin: reject 'return 0' at the verifier for 'void' hooks
> - Martin: prog_query returns all BPF_LSM_CGROUP, prog_info
> returns attach_btf_func_id
> - Andrii: split libbpf changes
> - Andrii: add field access test to test_progs, not test_verifier (still
> using asm though)
> - things that I haven't addressed, stating them here explicitly, let
> me know if some of these are still problematic:
> 1. Andrii: exposing only link-based api: seems like the changes
> to support non-link-based ones are minimal, couple of lines,
> so seems like it worth having it?
> 2. Alexei: applying cgroup_atype for all cgroup hooks, not only
> cgroup lsm: looks a bit harder to apply everywhere that I
> originally thought; with lsm cgroup, we have a shim_prog pointer where
> we store cgroup_atype; for non-lsm programs, we don't have a
> trace program where to store it, so we still need some kind
> of global table to map from "static" hook to "dynamic" slot.
> So I'm dropping this "can be easily extended" clause from the
> description for now. I have converted this whole machinery
> to an RCU-managed list to remove synchronize_rcu().
> - also note that I had to introduce new bpf_shim_tramp_link and
> moved refcnt there; we need something to manage new bpf_tramp_link
>
> v6:
> - remove active count & stats for shim program (Martin KaFai Lau)
> - remove NULL/error check for btf_vmlinux (Martin)
> - don't check cgroup_atype in bpf_cgroup_lsm_shim_release (Martin)
> - use old_prog (instead of passed one) in __cgroup_bpf_detach (Martin)
> - make sure attach_btf_id is the same in __cgroup_bpf_replace (Martin)
> - enable cgroup local storage and test it (Martin)
> - properly implement prog query and add bpftool & tests (Martin)
> - prohibit non-shared cgroup storage mode for BPF_LSM_CGROUP (Martin)
>
> v5:
> - __cgroup_bpf_run_lsm_socket remove NULL sock/sk checks (Martin KaFai Lau)
> - __cgroup_bpf_run_lsm_{socket,current} s/prog/shim_prog/ (Martin)
> - make sure bpf_lsm_find_cgroup_shim works for hooks without args (Martin)
> - __cgroup_bpf_attach make sure attach_btf_id is the same when replacing (Martin)
> - call bpf_cgroup_lsm_shim_release only for LSM_CGROUP (Martin)
> - drop BPF_LSM_CGROUP from bpf_attach_type_to_tramp (Martin)
> - drop jited check from cgroup_shim_find (Martin)
> - new patch to convert cgroup_bpf to hlist_node (Jakub Sitnicki)
> - new shim flavor for 'struct sock' + list of exceptions (Martin)
>
> v4:
> - fix build when jit is on but syscall is off
>
> v3:
> - add BPF_LSM_CGROUP to bpftool
> - use simple int instead of refcnt_t (to avoid use-after-free
> false positive)
>
> v2:
> - addressed build bot failures
>
> Stanislav Fomichev (11):
> bpf: add bpf_func_t and trampoline helpers
> bpf: convert cgroup_bpf.progs to hlist
> bpf: per-cgroup lsm flavor
> bpf: minimize number of allocated lsm slots per program
> bpf: implement BPF_PROG_QUERY for BPF_LSM_CGROUP
> bpf: allow writing to a subset of sock fields from lsm progtype
> libbpf: implement bpf_prog_query_opts
> libbpf: add lsm_cgoup_sock type
> bpftool: implement cgroup tree for BPF_LSM_CGROUP
> selftests/bpf: lsm_cgroup functional test
> selftests/bpf: verify lsm_cgroup struct sock access
>
> arch/x86/net/bpf_jit_comp.c | 24 +-
> include/linux/bpf-cgroup-defs.h | 11 +-
> include/linux/bpf-cgroup.h | 9 +-
> include/linux/bpf.h | 36 +-
> include/linux/bpf_lsm.h | 8 +
> include/linux/btf_ids.h | 3 +-
> include/uapi/linux/bpf.h | 6 +
> kernel/bpf/bpf_lsm.c | 103 ++++
> kernel/bpf/btf.c | 11 +
> kernel/bpf/cgroup.c | 487 +++++++++++++++---
> kernel/bpf/core.c | 2 +
> kernel/bpf/syscall.c | 14 +-
> kernel/bpf/trampoline.c | 244 ++++++++-
> kernel/bpf/verifier.c | 31 +-
> tools/bpf/bpftool/cgroup.c | 77 ++-
> tools/bpf/bpftool/common.c | 1 +
> tools/include/linux/btf_ids.h | 4 +-
> tools/include/uapi/linux/bpf.h | 6 +
> tools/lib/bpf/bpf.c | 42 +-
> tools/lib/bpf/bpf.h | 15 +
> tools/lib/bpf/libbpf.c | 2 +
> tools/lib/bpf/libbpf.map | 1 +
> .../selftests/bpf/prog_tests/lsm_cgroup.c | 346 +++++++++++++
> .../testing/selftests/bpf/progs/lsm_cgroup.c | 160 ++++++
> 24 files changed, 1480 insertions(+), 163 deletions(-)
> create mode 100644 tools/testing/selftests/bpf/prog_tests/lsm_cgroup.c
> create mode 100644 tools/testing/selftests/bpf/progs/lsm_cgroup.c
There are 4 test failures for test_progs in CI.
https://github.com/kernel-patches/bpf/runs/6511113546?check_suite_focus=true
All have error messages like:
At program exit the register R0 has value (0xffffffff; 0x0) should
have been in (0x0; 0x1)
Could you take a look?
next prev parent reply other threads:[~2022-05-19 23:34 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 22:55 [PATCH bpf-next v7 00/11] bpf: cgroup_sock lsm flavor Stanislav Fomichev
2022-05-18 22:55 ` [PATCH bpf-next v7 01/11] bpf: add bpf_func_t and trampoline helpers Stanislav Fomichev
2022-05-20 0:45 ` Yonghong Song
2022-05-21 0:03 ` Stanislav Fomichev
2022-05-18 22:55 ` [PATCH bpf-next v7 02/11] bpf: convert cgroup_bpf.progs to hlist Stanislav Fomichev
2022-05-18 22:55 ` [PATCH bpf-next v7 03/11] bpf: per-cgroup lsm flavor Stanislav Fomichev
2022-05-20 1:00 ` Yonghong Song
2022-05-21 0:03 ` Stanislav Fomichev
2022-05-23 15:41 ` Yonghong Song
2022-05-21 0:53 ` Martin KaFai Lau
2022-05-24 2:15 ` Stanislav Fomichev
2022-05-24 5:40 ` Martin KaFai Lau
2022-05-24 15:56 ` Stanislav Fomichev
2022-05-24 5:57 ` Martin KaFai Lau
2022-05-18 22:55 ` [PATCH bpf-next v7 04/11] bpf: minimize number of allocated lsm slots per program Stanislav Fomichev
2022-05-21 6:56 ` Martin KaFai Lau
2022-05-24 2:14 ` Stanislav Fomichev
2022-05-24 5:53 ` Martin KaFai Lau
2022-05-18 22:55 ` [PATCH bpf-next v7 05/11] bpf: implement BPF_PROG_QUERY for BPF_LSM_CGROUP Stanislav Fomichev
2022-05-19 2:31 ` kernel test robot
2022-05-19 14:57 ` kernel test robot
2022-05-23 23:23 ` Andrii Nakryiko
2022-05-24 2:15 ` Stanislav Fomichev
2022-05-24 3:48 ` Martin KaFai Lau
2022-05-24 15:55 ` Stanislav Fomichev
2022-05-24 17:50 ` Martin KaFai Lau
2022-05-24 23:45 ` Andrii Nakryiko
2022-05-25 4:03 ` Stanislav Fomichev
2022-05-25 4:39 ` Andrii Nakryiko
2022-05-25 16:01 ` Stanislav Fomichev
2022-05-25 17:02 ` Stanislav Fomichev
2022-05-25 20:39 ` Martin KaFai Lau
2022-05-25 21:25 ` sdf
2022-05-26 0:03 ` Martin KaFai Lau
2022-05-26 1:23 ` Martin KaFai Lau
2022-05-26 2:50 ` Stanislav Fomichev
2022-05-31 23:08 ` Andrii Nakryiko
2022-05-18 22:55 ` [PATCH bpf-next v7 06/11] bpf: allow writing to a subset of sock fields from lsm progtype Stanislav Fomichev
2022-05-18 22:55 ` [PATCH bpf-next v7 07/11] libbpf: implement bpf_prog_query_opts Stanislav Fomichev
2022-05-23 23:22 ` Andrii Nakryiko
2022-05-24 2:15 ` Stanislav Fomichev
2022-05-24 3:45 ` Andrii Nakryiko
2022-05-24 4:01 ` Martin KaFai Lau
2022-05-18 22:55 ` [PATCH bpf-next v7 08/11] libbpf: add lsm_cgoup_sock type Stanislav Fomichev
2022-05-23 23:26 ` Andrii Nakryiko
2022-05-24 2:15 ` Stanislav Fomichev
2022-05-18 22:55 ` [PATCH bpf-next v7 09/11] bpftool: implement cgroup tree for BPF_LSM_CGROUP Stanislav Fomichev
2022-05-18 22:55 ` [PATCH bpf-next v7 10/11] selftests/bpf: lsm_cgroup functional test Stanislav Fomichev
2022-05-18 22:55 ` [PATCH bpf-next v7 11/11] selftests/bpf: verify lsm_cgroup struct sock access Stanislav Fomichev
2022-05-23 23:33 ` Andrii Nakryiko
2022-05-24 2:15 ` Stanislav Fomichev
2022-05-24 3:46 ` Andrii Nakryiko
2022-05-19 23:34 ` Yonghong Song [this message]
2022-05-19 23:39 ` [PATCH bpf-next v7 00/11] bpf: cgroup_sock lsm flavor Stanislav Fomichev
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=3a732a8d-6e4f-0154-e317-795baa64022d@fb.com \
--to=yhs@fb.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub@cloudflare.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox