From: patchwork-bot+netdevbpf@kernel.org
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, kernel-team@meta.com, andrii@kernel.org,
eddyz87@gmail.com, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev
Subject: Re: [PATCH v2 bpf-next] selftests/bpf: Fix cgroup_xattr/read_cgroupfs_xattr
Date: Fri, 27 Jun 2025 21:40:06 +0000 [thread overview]
Message-ID: <175106040601.2068050.6481377720178421832.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250627191221.765921-1-song@kernel.org>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 27 Jun 2025 12:12:21 -0700 you wrote:
> cgroup_xattr/read_cgroupfs_xattr has two issues:
>
> 1. cgroup_xattr/read_cgroupfs_xattr messes up lo without creating a netns
> first. This causes issue with other tests.
>
> Fix this by using a different hook (lsm.s/file_open) and not messing
> with lo.
>
> [...]
Here is the summary with links:
- [v2,bpf-next] selftests/bpf: Fix cgroup_xattr/read_cgroupfs_xattr
https://git.kernel.org/bpf/bpf-next/c/bacdf5a0e69d
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:[~2025-06-27 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 19:12 [PATCH v2 bpf-next] selftests/bpf: Fix cgroup_xattr/read_cgroupfs_xattr Song Liu
2025-06-27 20:50 ` Eduard Zingerman
2025-06-27 21:19 ` Ihor Solodrai
2025-06-27 21:34 ` Alexei Starovoitov
2025-06-27 21:36 ` Ihor Solodrai
2025-06-27 21:38 ` Alexei Starovoitov
2025-06-27 21:56 ` Ihor Solodrai
2025-06-27 22:05 ` Ihor Solodrai
2025-06-27 23:19 ` Alexei Starovoitov
2025-06-30 21:49 ` Ihor Solodrai
2025-06-30 22:11 ` Alexei Starovoitov
2025-06-30 22:22 ` Ihor Solodrai
2025-06-27 21:40 ` 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=175106040601.2068050.6481377720178421832.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=kernel-team@meta.com \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
/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