From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev,
alexei.starovoitov@gmail.com, andrii@kernel.org, song@kernel.org,
haoluo@google.com, yonghong.song@linux.dev, daniel@iogearbox.net,
kpsingh@kernel.org, sdf@google.com, jolsa@kernel.org,
john.fastabend@gmail.com, houtao1@huawei.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Close cgrp fd before calling cleanup_cgroup_environment()
Date: Wed, 20 Dec 2023 02:30:22 +0000 [thread overview]
Message-ID: <170303942296.26103.7995929302760177863.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231219135727.2661527-1-houtao@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 19 Dec 2023 21:57:27 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> There is error log when htab-mem benchmark completes. The error log
> looks as follows:
>
> $ ./bench htab-mem -d1
> Setting up benchmark 'htab-mem'...
> Benchmark 'htab-mem' started.
> ......
> (cgroup_helpers.c:353: errno: Device or resource busy) umount cgroup2
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: Close cgrp fd before calling cleanup_cgroup_environment()
https://git.kernel.org/bpf/bpf-next/c/441c725ed592
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:[~2023-12-20 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 13:57 [PATCH bpf-next] selftests/bpf: Close cgrp fd before calling cleanup_cgroup_environment() Hou Tao
2023-12-20 2:30 ` 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=170303942296.26103.7995929302760177863.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=houtao1@huawei.com \
--cc=houtao@huaweicloud.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox