From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, kafai@fb.com, andrii@kernel.org,
songliubraving@fb.com, haoluo@google.com, yhs@fb.com,
ast@kernel.org, daniel@iogearbox.net, kpsingh@kernel.org,
davem@davemloft.net, kuba@kernel.org, sdf@google.com,
jolsa@kernel.org, john.fastabend@gmail.com, oss@lmb.io,
houtao1@huawei.com
Subject: Re: [PATCH bpf-next v2 0/2] Fix resource leaks in test_maps
Date: Thu, 22 Sep 2022 23:50:16 +0000 [thread overview]
Message-ID: <166389061612.10533.9582750586961600101.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220921070035.2016413-1-houtao@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 21 Sep 2022 15:00:33 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Hi,
>
> It is just a tiny patch set aims to fix the resource leaks in test_maps
> after test case succeeds or is skipped. And these leaks are spotted by
> using address sanitizer and checking the content of /proc/$pid/fd.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] selftests/bpf: Destroy the skeleton when CONFIG_PREEMPT is off
https://git.kernel.org/bpf/bpf-next/c/f5eb23b91c41
- [bpf-next,v2,2/2] selftests/bpf: Free the allocated resources after test case succeeds
https://git.kernel.org/bpf/bpf-next/c/103d002fb7d5
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:[~2022-09-22 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 7:00 [PATCH bpf-next v2 0/2] Fix resource leaks in test_maps Hou Tao
2022-09-21 7:00 ` [PATCH bpf-next v2 1/2] selftests/bpf: Destroy the skeleton when CONFIG_PREEMPT is off Hou Tao
2022-09-21 7:00 ` [PATCH bpf-next v2 2/2] selftests/bpf: Free the allocated resources after test case succeeds Hou Tao
2022-09-22 23: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=166389061612.10533.9582750586961600101.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=davem@davemloft.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=oss@lmb.io \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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.