From: patchwork-bot+netdevbpf@kernel.org
To: Hou Tao <houtao@huaweicloud.com>
Cc: bpf@vger.kernel.org, martin.lau@linux.dev, haoluo@google.com,
yhs@fb.com, andrii@kernel.org, song@kernel.org, ast@kernel.org,
daniel@iogearbox.net, kpsingh@kernel.org, sdf@google.com,
jolsa@kernel.org, john.fastabend@gmail.com, houtao1@huawei.com
Subject: Re: [PATCH bpf-next v3 0/3] bpf: Pin the start cgroup for cgroup iterator
Date: Mon, 21 Nov 2022 16:50:15 +0000 [thread overview]
Message-ID: <166904941577.16961.4100589791651140735.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221121073440.1828292-1-houtao@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 21 Nov 2022 15:34:37 +0800 you wrote:
> From: Hou Tao <houtao1@huawei.com>
>
> Hi,
>
> The patchset tries to fix the potential use-after-free problem in cgroup
> iterator. The problem is similar with the UAF problem fixed in map
> iterator and the fix is also similar: pinning the iterated resource in
> .init_seq_private() and unpinning it in .fini_seq_private(). An
> alternative fix is pinning iterator link when opening iterator fd, but
> it will make iterator link still being visible after the close of
> iterator link fd and the behavior is different with other link types, so
> just fixing the bug alone by pinning the start cgroup when creating
> cgroup iterator. Also adding a selftests to demonstrate the UAF problem
> when iterating a dead cgroup.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/3] bpf: Pin the start cgroup in cgroup_iter_seq_init()
https://git.kernel.org/bpf/bpf-next/c/1a5160d4d8fe
- [bpf-next,v3,2/3] selftests/bpf: Add cgroup helper remove_cgroup()
https://git.kernel.org/bpf/bpf-next/c/2a42461a8831
- [bpf-next,v3,3/3] selftests/bpf: Add test for cgroup iterator on a dead cgroup
https://git.kernel.org/bpf/bpf-next/c/8589e92675aa
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-11-21 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 7:34 [PATCH bpf-next v3 0/3] bpf: Pin the start cgroup for cgroup iterator Hou Tao
2022-11-21 7:34 ` [PATCH bpf-next v3 1/3] bpf: Pin the start cgroup in cgroup_iter_seq_init() Hou Tao
2022-11-21 16:27 ` Yonghong Song
2022-11-21 7:34 ` [PATCH bpf-next v3 2/3] selftests/bpf: Add cgroup helper remove_cgroup() Hou Tao
2022-11-21 7:34 ` [PATCH bpf-next v3 3/3] selftests/bpf: Add test for cgroup iterator on a dead cgroup Hou Tao
2022-11-21 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=166904941577.16961.4100589791651140735.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=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox