From: Eduard Zingerman <eddyz87@gmail.com>
To: Ihor Solodrai <ihor.solodrai@linux.dev>,
Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>,
andrii@kernel.org
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
mykolal@fb.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next 1/2] bpf: add bpf_dynptr_memset() kfunc
Date: Thu, 19 Jun 2025 10:19:20 -0700 [thread overview]
Message-ID: <7852f30ba177dc5b811bb0840ca0f301df2a8b58.camel@gmail.com> (raw)
In-Reply-To: <45390c6c-bd2a-4962-8222-1ad346f9908c@linux.dev>
On Thu, 2025-06-19 at 10:09 -0700, Ihor Solodrai wrote:
[...]
> But then, does memset even make sense for xdp/skb buffers?
Why not?
> Maybe -ENOTSUPP is more appropriate?
>
> I'd appreciate any hints.
I think Mykyta has kernel/trace/bpf_trace.c:__bpf_dynptr_copy_str() in mind.
next prev parent reply other threads:[~2025-06-19 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 22:33 [PATCH bpf-next 1/2] bpf: add bpf_dynptr_memset() kfunc Ihor Solodrai
2025-06-18 22:33 ` [PATCH bpf-next 2/2] selftests/bpf: add test cases for bpf_dynptr_memset() Ihor Solodrai
2025-06-18 23:44 ` [PATCH bpf-next 1/2] bpf: add bpf_dynptr_memset() kfunc Mykyta Yatsenko
2025-06-19 17:09 ` Ihor Solodrai
2025-06-19 17:19 ` Eduard Zingerman [this message]
2025-06-19 17:55 ` Ihor Solodrai
2025-06-19 17:57 ` Eduard Zingerman
2025-06-19 18:04 ` Ihor Solodrai
2025-06-19 18:13 ` Eduard Zingerman
2025-06-19 18:17 ` Eduard Zingerman
2025-06-23 21:38 ` Andrii Nakryiko
2025-06-23 21:45 ` Eduard Zingerman
2025-06-23 22:12 ` Andrii Nakryiko
2025-06-20 15:09 ` Mykyta Yatsenko
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=7852f30ba177dc5b811bb0840ca0f301df2a8b58.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=ihor.solodrai@linux.dev \
--cc=kernel-team@meta.com \
--cc=mykolal@fb.com \
--cc=mykyta.yatsenko5@gmail.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.