BPF List
 help / color / mirror / Atom feed
From: Yonghong Song <yhs@meta.com>
To: Hou Tao <houtao@huaweicloud.com>,
	bpf@vger.kernel.org, Yonghong Song <yhs@fb.com>
Cc: Martin KaFai Lau <martin.lau@linux.dev>,
	Andrii Nakryiko <andrii@kernel.org>, Song Liu <song@kernel.org>,
	Hao Luo <haoluo@google.com>, Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@google.com>, Jiri Olsa <jolsa@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	houtao1@huawei.com
Subject: Re: [PATCH bpf v2 1/3] bpf: Pin iterator link when opening iterator
Date: Fri, 11 Nov 2022 08:31:13 -0800	[thread overview]
Message-ID: <00e96d17-bde6-d060-7cc0-bf4a2a0065e0@meta.com> (raw)
In-Reply-To: <20221111063417.1603111-2-houtao@huaweicloud.com>



On 11/10/22 10:34 PM, Hou Tao wrote:
> From: Hou Tao <houtao1@huawei.com>
> 
> For many bpf iterator (e.g., cgroup iterator), iterator link acquires
> the reference of iteration target in .attach_target(), but iterator link
> may be closed before or in the middle of iteration, so iterator will
> need to acquire the reference of iteration target as well to prevent
> potential use-after-free. To avoid doing the acquisition in
> .init_seq_private() for each iterator type, just pin iterator link in
> iterator.
> 
> Fixes: d4ccaf58a847 ("bpf: Introduce cgroup iter")
> Signed-off-by: Hou Tao <houtao1@huawei.com>

Thanks. LGTM. Once this patch went through bpf and circulated back to
bpf-next, you can revert the change for the following patches:
    f0d2b2716d71  bpf: Acquire map uref in .init_seq_private for 
sock{map,hash} iterator
    3c5f6e698b5c  bpf: Acquire map uref in .init_seq_private for sock 
local storage map iterator
    ef1e93d2eeb5  bpf: Acquire map uref in .init_seq_private for hash 
map iterator
    f76fa6b33805  bpf: Acquire map uref in .init_seq_private for array 
map iterator
in bpf-next.

Acked-by: Yonghong Song <yhs@fb.com>

  reply	other threads:[~2022-11-11 16:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  6:34 [PATCH bpf v2 0/3] Pin iterator link when opening iterator Hou Tao
2022-11-11  6:34 ` [PATCH bpf v2 1/3] bpf: " Hou Tao
2022-11-11 16:31   ` Yonghong Song [this message]
2022-11-11 17:24     ` Hao Luo
2022-11-15 19:16   ` Martin KaFai Lau
2022-11-16  1:37     ` Alexei Starovoitov
2022-11-16  2:40       ` Hou Tao
2022-11-16  5:43         ` Alexei Starovoitov
2022-11-16  6:56           ` Hou Tao
2022-11-16  2:48       ` Hao Luo
2022-11-16  7:24         ` Hou Tao
2022-11-17  6:48         ` Martin KaFai Lau
2022-11-18  1:52           ` Hou Tao
2022-11-18  7:34             ` Martin KaFai Lau
2022-11-18 18:57               ` Hao Luo
2022-11-16  2:39     ` Hou Tao
2022-11-11  6:34 ` [PATCH bpf v2 2/3] selftests/bpf: Add cgroup helper remove_cgroup() Hou Tao
2022-11-11  6:34 ` [PATCH bpf v2 3/3] selftests/bpf: Add test for cgroup iterator on a dead cgroup Hou Tao
2022-11-11 18:00   ` Hao Luo

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=00e96d17-bde6-d060-7cc0-bf4a2a0065e0@meta.com \
    --to=yhs@meta.com \
    --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