From: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Tetsuo Handa
<penguin-kernel-1yMVhJb1mP/7nzcFbJAaVXf5DAMn2ifp@public.gmane.org>
Cc: Zefan Li <lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] cgroup,freezer: hold cpu_hotplug_lock before freezer_mutex in freezer_css_{online,offline}()
Date: Mon, 12 Jun 2023 06:43:30 -1000 [thread overview]
Message-ID: <ZIdLMv-ayau220Mp@slm.duckdns.org> (raw)
In-Reply-To: <69ab449f-1981-2d53-79fb-b2ac91ea9cef-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
On Sun, Jun 11, 2023 at 10:48:12PM +0900, Tetsuo Handa wrote:
> syzbot is again reporting circular locking dependency between
> cpu_hotplug_lock and freezer_mutex. Do like what we did with
> commit 57dcd64c7e036299 ("cgroup,freezer: hold cpu_hotplug_lock
> before freezer_mutex").
>
> Reported-by: syzbot <syzbot+2ab700fe1829880a2ec6-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
> Closes: https://syzkaller.appspot.com/bug?extid=2ab700fe1829880a2ec6
> Signed-off-by: Tetsuo Handa <penguin-kernel-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
> Tested-by: syzbot <syzbot+2ab700fe1829880a2ec6-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
Tagged w/ the same stable version as the earlier patch and applied to
cgroup/for-6.4-fixes.
Thanks.
--
tejun
prev parent reply other threads:[~2023-06-12 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 16:56 [syzbot] [cgroups?] possible deadlock in static_key_slow_inc (3) syzbot
[not found] ` <000000000000bd448705fda123f5-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2023-06-09 3:17 ` syzbot
[not found] ` <000000000000d1565005fda9cef1-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2023-06-11 13:48 ` [PATCH] cgroup,freezer: hold cpu_hotplug_lock before freezer_mutex in freezer_css_{online,offline}() Tetsuo Handa
[not found] ` <69ab449f-1981-2d53-79fb-b2ac91ea9cef-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
2023-06-12 16:43 ` Tejun Heo [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=ZIdLMv-ayau220Mp@slm.duckdns.org \
--to=tj-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org \
--cc=penguin-kernel-1yMVhJb1mP/7nzcFbJAaVXf5DAMn2ifp@public.gmane.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