From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin Lau <kafai@meta.com>, Kernel Team <kernel-team@meta.com>,
Eduard <eddyz87@gmail.com>, Mykyta Yatsenko <yatsenko@meta.com>
Subject: Re: [PATCH bpf-next v5 3/3] selftests/bpf: introduce tests for dynptr copy kfuncs
Date: Tue, 13 May 2025 12:13:20 +0100 [thread overview]
Message-ID: <584957e4-9cb7-4721-afda-c99b2eb1c0c5@gmail.com> (raw)
In-Reply-To: <CAADnVQKTVvXUXygnFASdoZc3d1WEPnVuxQWO8Fe8iQW6J9piMA@mail.gmail.com>
On 5/13/25 02:46, Alexei Starovoitov wrote:
> On Mon, May 12, 2025 at 1:54 PM Mykyta Yatsenko
> <mykyta.yatsenko5@gmail.com> wrote:
>> +dynptr/test_probe_read_user_str_dynptr # disabled until https://patchwork.kernel.org/project/linux-mm/patch/20250422131449.57177-1-mykyta.yatsenko5@gmail.com/ makes it into the bpf-next
> What is the status of it ?
> I don't see it in any trees.
It was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm just yesterday.
next prev parent reply other threads:[~2025-05-13 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 20:53 [PATCH bpf-next v5 0/3] Introduce kfuncs for memory reads into dynptrs Mykyta Yatsenko
2025-05-12 20:53 ` [PATCH bpf-next v5 1/3] helpers: make few bpf helpers public Mykyta Yatsenko
2025-05-12 20:53 ` [PATCH bpf-next v5 2/3] bpf: implement dynptr copy kfuncs Mykyta Yatsenko
2025-05-13 1:42 ` Alexei Starovoitov
2025-05-12 20:53 ` [PATCH bpf-next v5 3/3] selftests/bpf: introduce tests for " Mykyta Yatsenko
2025-05-13 1:46 ` Alexei Starovoitov
2025-05-13 11:13 ` Mykyta Yatsenko [this message]
2025-05-13 1:50 ` [PATCH bpf-next v5 0/3] Introduce kfuncs for memory reads into dynptrs patchwork-bot+netdevbpf
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=584957e4-9cb7-4721-afda-c99b2eb1c0c5@gmail.com \
--to=mykyta.yatsenko5@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.