From: patchwork-bot+netdevbpf@kernel.org
To: luyun <luyun_611@163.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev, jolsa@kernel.org,
emil@etsalapatis.com, ihor.solodrai@linux.dev, shuah@kernel.org,
yatsenko@meta.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix map fd leak in no-BTF wq test
Date: Thu, 15 Oct 2026 16:50:05 +0000 [thread overview]
Message-ID: <179208300503.4004131.2666615375051381971.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013030114.292157-1-luyun_611@163.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 13 Oct 2026 11:01:14 +0800 you wrote:
> From: Yun Lu <luyun@kylinos.cn>
>
> bpf_map__reuse_fd() duplicates the supplied file descriptor instead of
> taking ownership of it. test_failure_map_no_btf() closes the original
> map_fd only when reuse fails, leaking it when reuse succeeds, including
> when the test passes. Destroying the skeleton closes its own descriptor
> but leaves the original descriptor and its map reference alive.
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Fix map fd leak in no-BTF wq test
https://git.kernel.org/bpf/bpf-next/c/d3c9ecb8765d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-15 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 3:01 [PATCH bpf-next] selftests/bpf: Fix map fd leak in no-BTF wq test Yun Lu
2026-10-15 16:50 ` patchwork-bot+netdevbpf [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=179208300503.4004131.2666615375051381971.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luyun_611@163.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yatsenko@meta.com \
--cc=yonghong.song@linux.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 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.