From: Chen Ridong <chenridong@huawei.com>
To: <martin.lau@linux.dev>, <ast@kernel.org>, <daniel@iogearbox.net>,
<andrii@kernel.org>, <eddyz87@gmail.com>, <song@kernel.org>,
<yonghong.song@linux.dev>, <john.fastabend@gmail.com>,
<kpsingh@kernel.org>, <sdf@google.com>, <haoluo@google.com>,
<jolsa@kernel.org>, <tj@kernel.org>, <lizefan.x@bytedance.com>,
<hannes@cmpxchg.org>, <roman.gushchin@linux.dev>
Cc: <bpf@vger.kernel.org>, <cgroups@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/1] Fix deadlock caused by cgroup_mutex and cpu_hotplug_lock
Date: Sat, 17 Aug 2024 09:33:33 +0000 [thread overview]
Message-ID: <20240817093334.6062-1-chenridong@huawei.com> (raw)
changes from v1/v2:
- Optimize commit msg.
Link v1: https://lore.kernel.org/cgroups/20240607110313.2230669-1-chenridong@huawei.com/
Link v2: https://lore.kernel.org/cgroups/20240719025232.2143638-1-chenridong@huawei.com/
Chen Ridong (1):
cgroup: fix deadlock caused by cgroup_mutex and cpu_hotplug_lock
kernel/bpf/cgroup.c | 2 +-
kernel/cgroup/cgroup-internal.h | 1 +
kernel/cgroup/cgroup.c | 2 +-
3 files changed, 3 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2024-08-17 9:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 9:33 Chen Ridong [this message]
2024-08-17 9:33 ` [PATCH v3 1/1] cgroup: fix deadlock caused by cgroup_mutex and cpu_hotplug_lock Chen Ridong
2024-08-22 0:57 ` Chen Ridong
2024-08-30 2:08 ` Chen Ridong
2024-09-09 14:19 ` Michal Koutný
2024-09-10 1:31 ` Chen Ridong
2024-09-10 21:02 ` Roman Gushchin
2024-09-10 21:17 ` Tejun Heo
2024-09-12 1:33 ` Chen Ridong
2024-09-12 5:59 ` Tejun Heo
2024-09-11 11:15 ` Hillf Danton
2024-09-26 12:53 ` Michal Koutný
2024-09-27 11:25 ` Hillf Danton
2024-09-27 14:03 ` Michal Koutný
2024-09-28 8:11 ` Tetsuo Handa
2024-09-29 1:30 ` Chen Ridong
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=20240817093334.6062-1-chenridong@huawei.com \
--to=chenridong@huawei.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=martin.lau@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=tj@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