public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin KaFai Lau <martin.lau@linux.dev>
To: Abel Wu <wuyun.abel@bytedance.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>, David Vernet <void@manifault.com>,
	"open list:BPF [STORAGE & CGROUPS]" <bpf@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf v2] bpf: Fix deadlock when freeing cgroup storage
Date: Fri, 24 Jan 2025 12:20:48 -0800	[thread overview]
Message-ID: <02c69185-1477-485c-af4f-a46f7aadadab@linux.dev> (raw)
In-Reply-To: <20241221061018.37717-1-wuyun.abel@bytedance.com>

On 12/20/24 10:10 PM, Abel Wu wrote:
> The following commit
> bc235cdb423a ("bpf: Prevent deadlock from recursive bpf_task_storage_[get|delete]")
> first introduced deadlock prevention for fentry/fexit programs attaching
> on bpf_task_storage helpers. That commit also employed the logic in map
> free path in its v6 version.
> 
> Later bpf_cgrp_storage was first introduced in
> c4bcfb38a95e ("bpf: Implement cgroup storage available to non-cgroup-attached bpf progs")
> which faces the same issue as bpf_task_storage, instead of its busy
> counter, NULL was passed to bpf_local_storage_map_free() which opened
> a window to cause deadlock:
> 
> 	<TASK>
> 		(acquiring local_storage->lock)
> 	_raw_spin_lock_irqsave+0x3d/0x50
> 	bpf_local_storage_update+0xd1/0x460
> 	bpf_cgrp_storage_get+0x109/0x130
> 	bpf_prog_a4d4a370ba857314_cgrp_ptr+0x139/0x170
> 	? __bpf_prog_enter_recur+0x16/0x80
> 	bpf_trampoline_6442485186+0x43/0xa4
> 	cgroup_storage_ptr+0x9/0x20
> 		(holding local_storage->lock)
> 	bpf_selem_unlink_storage_nolock.constprop.0+0x135/0x160
> 	bpf_selem_unlink_storage+0x6f/0x110
> 	bpf_local_storage_map_free+0xa2/0x110
> 	bpf_map_free_deferred+0x5b/0x90
> 	process_one_work+0x17c/0x390
> 	worker_thread+0x251/0x360
> 	kthread+0xd2/0x100
> 	ret_from_fork+0x34/0x50
> 	ret_from_fork_asm+0x1a/0x30
> 	</TASK>
> 
> Progs:
>   - A: SEC("fentry/cgroup_storage_ptr")

The v1 thread has suggested using notrace in a few functions. I didn't see any 
counterarguments that wouldn't be sufficient.

imo, that should be a better option instead of having more unnecessary failures 
in all other normal use cases which will not be interested in tracing 
cgroup_storage_ptr().

pw-bot: cr

>     - cgid (BPF_MAP_TYPE_HASH)
> 	Record the id of the cgroup the current task belonging
> 	to in this hash map, using the address of the cgroup
> 	as the map key.
>     - cgrpa (BPF_MAP_TYPE_CGRP_STORAGE)
> 	If current task is a kworker, lookup the above hash
> 	map using function parameter @owner as the key to get
> 	its corresponding cgroup id which is then used to get
> 	a trusted pointer to the cgroup through
> 	bpf_cgroup_from_id(). This trusted pointer can then
> 	be passed to bpf_cgrp_storage_get() to finally trigger
> 	the deadlock issue.
>   - B: SEC("tp_btf/sys_enter")
>     - cgrpb (BPF_MAP_TYPE_CGRP_STORAGE)
> 	The only purpose of this prog is to fill Prog A's
> 	hash map by calling bpf_cgrp_storage_get() for as
> 	many userspace tasks as possible.
> 
> Steps to reproduce:
>   - Run A;
>   - while (true) { Run B; Destroy B; }
> 
> Fix this issue by passing its busy counter to the free procedure so
> it can be properly incremented before storage/smap locking.
> 
> Fixes: c4bcfb38a95e ("bpf: Implement cgroup storage available to non-cgroup-attached bpf progs")
> Signed-off-by: Abel Wu <wuyun.abel@bytedance.com>
> ---
>   kernel/bpf/bpf_cgrp_storage.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/bpf/bpf_cgrp_storage.c b/kernel/bpf/bpf_cgrp_storage.c
> index 20f05de92e9c..7996fcea3755 100644
> --- a/kernel/bpf/bpf_cgrp_storage.c
> +++ b/kernel/bpf/bpf_cgrp_storage.c
> @@ -154,7 +154,7 @@ static struct bpf_map *cgroup_storage_map_alloc(union bpf_attr *attr)
>   
>   static void cgroup_storage_map_free(struct bpf_map *map)
>   {
> -	bpf_local_storage_map_free(map, &cgroup_cache, NULL);
> +	bpf_local_storage_map_free(map, &cgroup_cache, &bpf_cgrp_storage_busy);
>   }
>   
>   /* *gfp_flags* is a hidden argument provided by the verifier */


  parent reply	other threads:[~2025-01-24 20:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-21  6:10 [PATCH bpf v2] bpf: Fix deadlock when freeing cgroup storage Abel Wu
2025-01-23 18:01 ` Abel Wu
2025-01-24 20:20 ` Martin KaFai Lau [this message]
2025-01-26  9:31   ` Abel Wu
2025-01-27 22:15     ` Alexei Starovoitov
2025-01-27 23:05       ` Martin KaFai Lau
2025-01-29  6:23         ` Abel Wu
2025-01-30  2:40           ` Alexei Starovoitov

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=02c69185-1477-485c-af4f-a46f7aadadab@linux.dev \
    --to=martin.lau@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=void@manifault.com \
    --cc=wuyun.abel@bytedance.com \
    --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