From: Yonghong Song <yonghong.song@linux.dev>
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
eddyz87@gmail.com
Cc: Mykyta Yatsenko <yatsenko@meta.com>
Subject: Re: [PATCH bpf-next v3 4/4] selftests/bpf: test freplace from user namespace
Date: Fri, 7 Mar 2025 21:12:26 -0800 [thread overview]
Message-ID: <02caed19-ae4a-4c7e-bad6-449b4f157322@linux.dev> (raw)
In-Reply-To: <20250307212934.181996-5-mykyta.yatsenko5@gmail.com>
On 3/7/25 1:29 PM, Mykyta Yatsenko wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
>
> Add selftests to verify that it is possible to load freplace program
> from user namespace if BPF token is initialized by bpf_object__prepare
> before calling bpf_program__set_attach_target.
> Negative test is added as well.
>
> Modified type of the priv_prog to xdp, as kprobe did not work on aarch64
> and s390x.
>
> Signed-off-by: Mykyta Yatsenko <yatsenko@meta.com>
Acked-by: Yonghong Song <yonghong.song@linux.dev>
prev parent reply other threads:[~2025-03-08 5:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 21:29 [PATCH bpf-next v3 0/4] Support freplace prog from user namespace Mykyta Yatsenko
2025-03-07 21:29 ` [PATCH bpf-next v3 1/4] bpf: BPF token support for BPF_BTF_GET_FD_BY_ID Mykyta Yatsenko
2025-03-08 4:53 ` Yonghong Song
2025-03-07 21:29 ` [PATCH bpf-next v3 2/4] bpf: return prog btf_id without capable check Mykyta Yatsenko
2025-03-08 4:54 ` Yonghong Song
2025-03-07 21:29 ` [PATCH bpf-next v3 3/4] libbpf: pass BPF token from find_prog_btf_id to BPF_BTF_GET_FD_BY_ID Mykyta Yatsenko
2025-03-08 5:02 ` Yonghong Song
2025-03-07 21:29 ` [PATCH bpf-next v3 4/4] selftests/bpf: test freplace from user namespace Mykyta Yatsenko
2025-03-08 5:12 ` Yonghong Song [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=02caed19-ae4a-4c7e-bad6-449b4f157322@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=yatsenko@meta.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