From: Eduard Zingerman <eddyz87@gmail.com>
To: Yureka Lilian <yuka@yuka.dev>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Hao Luo <haoluo@google.com>, Jiri Olsa <jolsa@kernel.org>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] bpf: fix reuse of DEVMAP
Date: Wed, 13 Aug 2025 15:01:16 -0700 [thread overview]
Message-ID: <32575e7b7d714aad8d79f851ad00b8241c8ce277.camel@gmail.com> (raw)
In-Reply-To: <20250813200912.3523279-1-yuka@yuka.dev>
On Wed, 2025-08-13 at 22:09 +0200, Yureka Lilian wrote:
> This patch series includes the previous fix to libbpf for re-using DEVMAP
> maps, but modifies it to preserve compatibility with older kernels, thanks
> to the feedback given by Martin KaFai Lau.
>
> Additionally adds a basic selftest covering the re-use of DEVMAP maps, as
> requested by Eduard Zingerman.
Nit: could you please use tag `libbpf` instead of `bpf`?
>
> Yureka Lilian (2):
> bpf: fix reuse of DEVMAP
> bpf: add test for DEVMAP reuse
>
> tools/lib/bpf/libbpf.c | 14 +++-
> .../bpf/prog_tests/pinning_devmap_reuse.c | 68 +++++++++++++++++++
> .../selftests/bpf/progs/test_pinning_devmap.c | 20 ++++++
> 3 files changed, 101 insertions(+), 1 deletion(-)
> create mode 100644 tools/testing/selftests/bpf/prog_tests/pinning_devmap_reuse.c
> create mode 100644 tools/testing/selftests/bpf/progs/test_pinning_devmap.c
prev parent reply other threads:[~2025-08-13 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 20:09 Yureka Lilian
2025-08-13 20:09 ` [PATCH v2 1/2] " Yureka Lilian
2025-08-13 21:59 ` Eduard Zingerman
2025-08-13 22:49 ` Andrii Nakryiko
2025-08-13 20:09 ` [PATCH v2 2/2] bpf: add test for DEVMAP reuse Yureka Lilian
2025-08-13 21:54 ` Eduard Zingerman
2025-08-13 22:01 ` Eduard Zingerman [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=32575e7b7d714aad8d79f851ad00b8241c8ce277.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
--cc=yuka@yuka.dev \
/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
all inboxes | Powered by JetHome®