* [syzbot] possible deadlock in static_key_slow_inc (2)
@ 2022-11-02 10:36 syzbot
[not found] ` <00000000000009483d05ec7a6b93-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
0 siblings, 1 reply; 5+ messages in thread
From: syzbot @ 2022-11-02 10:36 UTC (permalink / raw)
To: cgroups-u79uwXL29TY76Z2rM5mHXA, hannes-druUgvl0LCNAfugRpC6u6w,
linux-kernel-u79uwXL29TY76Z2rM5mHXA,
lizefan.x-EC8Uxl6Npydl57MIdRCFDg, netdev-u79uwXL29TY76Z2rM5mHXA,
syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw, tj-DgEjT+Ai2ygdnm+yROfE0A
Hello,
syzbot found the following issue on:
HEAD commit: a2c65a9d0568 net: dsa: fall back to default tagger if we c..
git tree: net
console+strace: https://syzkaller.appspot.com/x/log.txt?x=10cfb046880000
kernel config: https://syzkaller.appspot.com/x/.config?x=a66c6c673fb555e8
dashboard link: https://syzkaller.appspot.com/bug?extid=c39682e86c9d84152f93
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=159ad4fc880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=159d8591880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c43fc9428e96/disk-a2c65a9d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ef96432b3e62/vmlinux-a2c65a9d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee926615bbfc/bzImage-a2c65a9d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c39682e86c9d84152f93-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org
======================================================
WARNING: possible circular locking dependency detected
6.1.0-rc2-syzkaller-00201-ga2c65a9d0568 #0 Not tainted
------------------------------------------------------
syz-executor229/3606 is trying to acquire lock:
ffffffff8be35130 (cpu_hotplug_lock){++++}-{0:0}, at: static_key_slow_inc+0xe/0x20 kernel/jump_label.c:158
but task is already holding lock:
ffffffff8bfda0c8 (freezer_mutex){+.+.}-{3:3}, at: freezer_change_state kernel/cgroup/legacy_freezer.c:387 [inline]
ffffffff8bfda0c8 (freezer_mutex){+.+.}-{3:3}, at: freezer_write+0x98/0xa50 kernel/cgroup/legacy_freezer.c:426
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (freezer_mutex){+.+.}-{3:3}:
__mutex_lock_common kernel/locking/mutex.c:603 [inline]
__mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
freezer_attach+0x70/0x1f0 kernel/cgroup/legacy_freezer.c:163
cgroup_migrate_execute+0xbcf/0x1230 kernel/cgroup/cgroup.c:2615
cgroup_attach_task+0x41c/0x870 kernel/cgroup/cgroup.c:2906
__cgroup1_procs_write.constprop.0+0x3be/0x4b0 kernel/cgroup/cgroup-v1.c:523
cgroup_file_write+0x1de/0x770 kernel/cgroup/cgroup.c:4057
kernfs_fop_write_iter+0x3f8/0x610 fs/kernfs/file.c:330
call_write_iter include/linux/fs.h:2191 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x9e9/0xdd0 fs/read_write.c:584
ksys_write+0x127/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #1 (cgroup_threadgroup_rwsem){++++}-{0:0}:
percpu_down_write+0x4f/0x390 kernel/locking/percpu-rwsem.c:227
cgroup_attach_lock kernel/cgroup/cgroup.c:2431 [inline]
cgroup_procs_write_start+0x151/0x630 kernel/cgroup/cgroup.c:2935
__cgroup_procs_write+0xd7/0x650 kernel/cgroup/cgroup.c:5135
cgroup_procs_write+0x22/0x50 kernel/cgroup/cgroup.c:5171
cgroup_file_write+0x1de/0x770 kernel/cgroup/cgroup.c:4057
kernfs_fop_write_iter+0x3f8/0x610 fs/kernfs/file.c:330
call_write_iter include/linux/fs.h:2191 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x9e9/0xdd0 fs/read_write.c:584
ksys_write+0x127/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
-> #0 (cpu_hotplug_lock){++++}-{0:0}:
check_prev_add kernel/locking/lockdep.c:3097 [inline]
check_prevs_add kernel/locking/lockdep.c:3216 [inline]
validate_chain kernel/locking/lockdep.c:3831 [inline]
__lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5055
lock_acquire kernel/locking/lockdep.c:5668 [inline]
lock_acquire+0x1df/0x630 kernel/locking/lockdep.c:5633
percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
cpus_read_lock+0x3e/0x140 kernel/cpu.c:310
static_key_slow_inc+0xe/0x20 kernel/jump_label.c:158
freezer_apply_state+0x1e1/0x260 kernel/cgroup/legacy_freezer.c:353
freezer_change_state kernel/cgroup/legacy_freezer.c:398 [inline]
freezer_write+0x571/0xa50 kernel/cgroup/legacy_freezer.c:426
cgroup_file_write+0x1de/0x770 kernel/cgroup/cgroup.c:4057
kernfs_fop_write_iter+0x3f8/0x610 fs/kernfs/file.c:330
call_write_iter include/linux/fs.h:2191 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x9e9/0xdd0 fs/read_write.c:584
ksys_write+0x127/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
other info that might help us debug this:
Chain exists of:
cpu_hotplug_lock --> cgroup_threadgroup_rwsem --> freezer_mutex
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(freezer_mutex);
lock(cgroup_threadgroup_rwsem);
lock(freezer_mutex);
lock(cpu_hotplug_lock);
*** DEADLOCK ***
4 locks held by syz-executor229/3606:
#0: ffff888079bc2460 (sb_writers#10){.+.+}-{0:0}, at: ksys_write+0x127/0x250 fs/read_write.c:637
#1: ffff88801fa91c88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x28c/0x610 fs/kernfs/file.c:321
#2: ffff888145b99a00 (kn->active#56){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x2b0/0x610 fs/kernfs/file.c:322
#3: ffffffff8bfda0c8 (freezer_mutex){+.+.}-{3:3}, at: freezer_change_state kernel/cgroup/legacy_freezer.c:387 [inline]
#3: ffffffff8bfda0c8 (freezer_mutex){+.+.}-{3:3}, at: freezer_write+0x98/0xa50 kernel/cgroup/legacy_freezer.c:426
stack backtrace:
CPU: 0 PID: 3606 Comm: syz-executor229 Not tainted 6.1.0-rc2-syzkaller-00201-ga2c65a9d0568 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2177
check_prev_add kernel/locking/lockdep.c:3097 [inline]
check_prevs_add kernel/locking/lockdep.c:3216 [inline]
validate_chain kernel/locking/lockdep.c:3831 [inline]
__lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5055
lock_acquire kernel/locking/lockdep.c:5668 [inline]
lock_acquire+0x1df/0x630 kernel/locking/lockdep.c:5633
percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
cpus_read_lock+0x3e/0x140 kernel/cpu.c:310
static_key_slow_inc+0xe/0x20 kernel/jump_label.c:158
freezer_apply_state+0x1e1/0x260 kernel/cgroup/legacy_freezer.c:353
freezer_change_state kernel/cgroup/legacy_freezer.c:398 [inline]
freezer_write+0x571/0xa50 kernel/cgroup/legacy_freezer.c:426
cgroup_file_write+0x1de/0x770 kernel/cgroup/cgroup.c:4057
kernfs_fop_write_iter+0x3f8/0x610 fs/kernfs/file.c:330
call_write_iter include/linux/fs.h:2191 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x9e9/0xdd0 fs/read_write.c:584
ksys_write+0x127/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fe89501f769
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 15 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff9816df18 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fe89501f769
RDX: 0000000000000007 RSI: 0000000020000040 RDI: 0000000000000004
RBP: 0000000000000000 R08: 00007fff9816df40 R09: 00007fff9816df40
R10: 00007fff9816df40 R11: 0000000000000246 R12: 00007fff9816df3c
R13: 00007fff9816df50 R14: 00007fff9816df90 R15: 0000000000000000
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH] cgroup,freezer: hold cpu_hotplug_lock before freezer_mutex
[not found] ` <00000000000009483d05ec7a6b93-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
@ 2023-04-05 13:15 ` Tetsuo Handa
[not found] ` <695b8d1c-6b7a-91b1-6941-c459cab038b0-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
0 siblings, 1 reply; 5+ messages in thread
From: Tetsuo Handa @ 2023-04-05 13:15 UTC (permalink / raw)
To: Peter Zijlstra, Ingo Molnar, Rafael J. Wysocki, Tejun Heo,
Zefan Li, Johannes Weiner
Cc: Cgroups, syzbot, syzkaller-bugs, Hillf Danton
syzbot is reporting circular locking dependency between cpu_hotplug_lock
and freezer_mutex, for commit f5d39b020809 ("freezer,sched: Rewrite core
freezer logic") replaced atomic_inc() in freezer_apply_state() with
static_branch_inc() which holds cpu_hotplug_lock.
cpu_hotplug_lock => cgroup_threadgroup_rwsem => freezer_mutex
cgroup_file_write() {
cgroup_procs_write() {
__cgroup_procs_write() {
cgroup_procs_write_start() {
cgroup_attach_lock() {
cpus_read_lock() {
percpu_down_read(&cpu_hotplug_lock);
}
percpu_down_write(&cgroup_threadgroup_rwsem);
}
}
cgroup_attach_task() {
cgroup_migrate() {
cgroup_migrate_execute() {
freezer_attach() {
mutex_lock(&freezer_mutex);
(...snipped...)
}
}
}
}
(...snipped...)
}
}
}
freezer_mutex => cpu_hotplug_lock
cgroup_file_write() {
freezer_write() {
freezer_change_state() {
mutex_lock(&freezer_mutex);
freezer_apply_state() {
static_branch_inc(&freezer_active) {
static_key_slow_inc() {
cpus_read_lock();
static_key_slow_inc_cpuslocked();
cpus_read_unlock();
}
}
}
mutex_unlock(&freezer_mutex);
}
}
}
Swap locking order by moving cpus_read_lock() in freezer_apply_state()
to before mutex_lock(&freezer_mutex) in freezer_change_state().
Reported-by: syzbot <syzbot+c39682e86c9d84152f93-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
Link: https://syzkaller.appspot.com/bug?extid=c39682e86c9d84152f93
Suggested-by: Hillf Danton <hdanton-k+cT0dCbe1g@public.gmane.org>
Fixes: f5d39b020809 ("freezer,sched: Rewrite core freezer logic")
Signed-off-by: Tetsuo Handa <penguin-kernel-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
---
kernel/cgroup/legacy_freezer.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/kernel/cgroup/legacy_freezer.c b/kernel/cgroup/legacy_freezer.c
index 1b6b21851e9d..936473203a6b 100644
--- a/kernel/cgroup/legacy_freezer.c
+++ b/kernel/cgroup/legacy_freezer.c
@@ -22,6 +22,7 @@
#include <linux/freezer.h>
#include <linux/seq_file.h>
#include <linux/mutex.h>
+#include <linux/cpu.h>
/*
* A cgroup is freezing if any FREEZING flags are set. FREEZING_SELF is
@@ -350,7 +351,7 @@ static void freezer_apply_state(struct freezer *freezer, bool freeze,
if (freeze) {
if (!(freezer->state & CGROUP_FREEZING))
- static_branch_inc(&freezer_active);
+ static_branch_inc_cpuslocked(&freezer_active);
freezer->state |= state;
freeze_cgroup(freezer);
} else {
@@ -361,7 +362,7 @@ static void freezer_apply_state(struct freezer *freezer, bool freeze,
if (!(freezer->state & CGROUP_FREEZING)) {
freezer->state &= ~CGROUP_FROZEN;
if (was_freezing)
- static_branch_dec(&freezer_active);
+ static_branch_dec_cpuslocked(&freezer_active);
unfreeze_cgroup(freezer);
}
}
@@ -379,6 +380,7 @@ static void freezer_change_state(struct freezer *freezer, bool freeze)
{
struct cgroup_subsys_state *pos;
+ cpus_read_lock();
/*
* Update all its descendants in pre-order traversal. Each
* descendant will try to inherit its parent's FREEZING state as
@@ -407,6 +409,7 @@ static void freezer_change_state(struct freezer *freezer, bool freeze)
}
rcu_read_unlock();
mutex_unlock(&freezer_mutex);
+ cpus_read_unlock();
}
static ssize_t freezer_write(struct kernfs_open_file *of,
--
2.34.1
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH] cgroup,freezer: hold cpu_hotplug_lock before freezer_mutex
[not found] ` <695b8d1c-6b7a-91b1-6941-c459cab038b0-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
@ 2023-04-05 13:28 ` Peter Zijlstra
2023-04-05 13:57 ` Mukesh Ojha
2023-04-12 17:31 ` Tejun Heo
2 siblings, 0 replies; 5+ messages in thread
From: Peter Zijlstra @ 2023-04-05 13:28 UTC (permalink / raw)
To: Tetsuo Handa
Cc: Ingo Molnar, Rafael J. Wysocki, Tejun Heo, Zefan Li,
Johannes Weiner, Cgroups, syzbot, syzkaller-bugs, Hillf Danton
On Wed, Apr 05, 2023 at 10:15:32PM +0900, Tetsuo Handa wrote:
> syzbot is reporting circular locking dependency between cpu_hotplug_lock
> and freezer_mutex, for commit f5d39b020809 ("freezer,sched: Rewrite core
> freezer logic") replaced atomic_inc() in freezer_apply_state() with
> static_branch_inc() which holds cpu_hotplug_lock.
>
> cpu_hotplug_lock => cgroup_threadgroup_rwsem => freezer_mutex
>
> cgroup_file_write() {
> cgroup_procs_write() {
> __cgroup_procs_write() {
> cgroup_procs_write_start() {
> cgroup_attach_lock() {
> cpus_read_lock() {
> percpu_down_read(&cpu_hotplug_lock);
> }
> percpu_down_write(&cgroup_threadgroup_rwsem);
> }
> }
> cgroup_attach_task() {
> cgroup_migrate() {
> cgroup_migrate_execute() {
> freezer_attach() {
> mutex_lock(&freezer_mutex);
> (...snipped...)
> }
> }
> }
> }
> (...snipped...)
> }
> }
> }
>
> freezer_mutex => cpu_hotplug_lock
>
> cgroup_file_write() {
> freezer_write() {
> freezer_change_state() {
> mutex_lock(&freezer_mutex);
> freezer_apply_state() {
> static_branch_inc(&freezer_active) {
> static_key_slow_inc() {
> cpus_read_lock();
> static_key_slow_inc_cpuslocked();
> cpus_read_unlock();
> }
> }
> }
> mutex_unlock(&freezer_mutex);
> }
> }
> }
>
> Swap locking order by moving cpus_read_lock() in freezer_apply_state()
> to before mutex_lock(&freezer_mutex) in freezer_change_state().
>
> Reported-by: syzbot <syzbot+c39682e86c9d84152f93-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
> Link: https://syzkaller.appspot.com/bug?extid=c39682e86c9d84152f93
> Suggested-by: Hillf Danton <hdanton-k+cT0dCbe1g@public.gmane.org>
> Fixes: f5d39b020809 ("freezer,sched: Rewrite core freezer logic")
> Signed-off-by: Tetsuo Handa <penguin-kernel-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
Thanks!
Acked-by: Peter Zijlstra (Intel) <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
> ---
> kernel/cgroup/legacy_freezer.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/cgroup/legacy_freezer.c b/kernel/cgroup/legacy_freezer.c
> index 1b6b21851e9d..936473203a6b 100644
> --- a/kernel/cgroup/legacy_freezer.c
> +++ b/kernel/cgroup/legacy_freezer.c
> @@ -22,6 +22,7 @@
> #include <linux/freezer.h>
> #include <linux/seq_file.h>
> #include <linux/mutex.h>
> +#include <linux/cpu.h>
>
> /*
> * A cgroup is freezing if any FREEZING flags are set. FREEZING_SELF is
> @@ -350,7 +351,7 @@ static void freezer_apply_state(struct freezer *freezer, bool freeze,
>
> if (freeze) {
> if (!(freezer->state & CGROUP_FREEZING))
> - static_branch_inc(&freezer_active);
> + static_branch_inc_cpuslocked(&freezer_active);
> freezer->state |= state;
> freeze_cgroup(freezer);
> } else {
> @@ -361,7 +362,7 @@ static void freezer_apply_state(struct freezer *freezer, bool freeze,
> if (!(freezer->state & CGROUP_FREEZING)) {
> freezer->state &= ~CGROUP_FROZEN;
> if (was_freezing)
> - static_branch_dec(&freezer_active);
> + static_branch_dec_cpuslocked(&freezer_active);
> unfreeze_cgroup(freezer);
> }
> }
> @@ -379,6 +380,7 @@ static void freezer_change_state(struct freezer *freezer, bool freeze)
> {
> struct cgroup_subsys_state *pos;
>
> + cpus_read_lock();
> /*
> * Update all its descendants in pre-order traversal. Each
> * descendant will try to inherit its parent's FREEZING state as
> @@ -407,6 +409,7 @@ static void freezer_change_state(struct freezer *freezer, bool freeze)
> }
> rcu_read_unlock();
> mutex_unlock(&freezer_mutex);
> + cpus_read_unlock();
> }
>
> static ssize_t freezer_write(struct kernfs_open_file *of,
> --
> 2.34.1
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] cgroup,freezer: hold cpu_hotplug_lock before freezer_mutex
[not found] ` <695b8d1c-6b7a-91b1-6941-c459cab038b0-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
2023-04-05 13:28 ` Peter Zijlstra
@ 2023-04-05 13:57 ` Mukesh Ojha
2023-04-12 17:31 ` Tejun Heo
2 siblings, 0 replies; 5+ messages in thread
From: Mukesh Ojha @ 2023-04-05 13:57 UTC (permalink / raw)
To: Tetsuo Handa, Peter Zijlstra, Ingo Molnar, Rafael J. Wysocki,
Tejun Heo, Zefan Li, Johannes Weiner
Cc: Cgroups, syzbot, syzkaller-bugs, Hillf Danton
On 4/5/2023 6:45 PM, Tetsuo Handa wrote:
> syzbot is reporting circular locking dependency between cpu_hotplug_lock
> and freezer_mutex, for commit f5d39b020809 ("freezer,sched: Rewrite core
> freezer logic") replaced atomic_inc() in freezer_apply_state() with
> static_branch_inc() which holds cpu_hotplug_lock.
>
> cpu_hotplug_lock => cgroup_threadgroup_rwsem => freezer_mutex
>
> cgroup_file_write() {
> cgroup_procs_write() {
> __cgroup_procs_write() {
> cgroup_procs_write_start() {
> cgroup_attach_lock() {
> cpus_read_lock() {
> percpu_down_read(&cpu_hotplug_lock);
> }
> percpu_down_write(&cgroup_threadgroup_rwsem);
> }
> }
> cgroup_attach_task() {
> cgroup_migrate() {
> cgroup_migrate_execute() {
> freezer_attach() {
> mutex_lock(&freezer_mutex);
> (...snipped...)
> }
> }
> }
> }
> (...snipped...)
> }
> }
> }
>
> freezer_mutex => cpu_hotplug_lock
>
> cgroup_file_write() {
> freezer_write() {
> freezer_change_state() {
> mutex_lock(&freezer_mutex);
> freezer_apply_state() {
> static_branch_inc(&freezer_active) {
> static_key_slow_inc() {
> cpus_read_lock();
> static_key_slow_inc_cpuslocked();
> cpus_read_unlock();
> }
> }
> }
> mutex_unlock(&freezer_mutex);
> }
> }
> }
>
> Swap locking order by moving cpus_read_lock() in freezer_apply_state()
> to before mutex_lock(&freezer_mutex) in freezer_change_state().
>
> Reported-by: syzbot <syzbot+c39682e86c9d84152f93-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
> Link: https://syzkaller.appspot.com/bug?extid=c39682e86c9d84152f93
> Suggested-by: Hillf Danton <hdanton-k+cT0dCbe1g@public.gmane.org>
> Fixes: f5d39b020809 ("freezer,sched: Rewrite core freezer logic")
> Signed-off-by: Tetsuo Handa <penguin-kernel-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
> ---
> kernel/cgroup/legacy_freezer.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/cgroup/legacy_freezer.c b/kernel/cgroup/legacy_freezer.c
> index 1b6b21851e9d..936473203a6b 100644
> --- a/kernel/cgroup/legacy_freezer.c
> +++ b/kernel/cgroup/legacy_freezer.c
> @@ -22,6 +22,7 @@
> #include <linux/freezer.h>
> #include <linux/seq_file.h>
> #include <linux/mutex.h>
> +#include <linux/cpu.h>
>
> /*
> * A cgroup is freezing if any FREEZING flags are set. FREEZING_SELF is
> @@ -350,7 +351,7 @@ static void freezer_apply_state(struct freezer *freezer, bool freeze,
>
> if (freeze) {
> if (!(freezer->state & CGROUP_FREEZING))
> - static_branch_inc(&freezer_active);
> + static_branch_inc_cpuslocked(&freezer_active);
> freezer->state |= state;
> freeze_cgroup(freezer);
> } else {
> @@ -361,7 +362,7 @@ static void freezer_apply_state(struct freezer *freezer, bool freeze,
> if (!(freezer->state & CGROUP_FREEZING)) {
> freezer->state &= ~CGROUP_FROZEN;
> if (was_freezing)
> - static_branch_dec(&freezer_active);
> + static_branch_dec_cpuslocked(&freezer_active);
> unfreeze_cgroup(freezer);
> }
> }
> @@ -379,6 +380,7 @@ static void freezer_change_state(struct freezer *freezer, bool freeze)
> {
> struct cgroup_subsys_state *pos;
>
> + cpus_read_lock();
> /*
> * Update all its descendants in pre-order traversal. Each
> * descendant will try to inherit its parent's FREEZING state as
> @@ -407,6 +409,7 @@ static void freezer_change_state(struct freezer *freezer, bool freeze)
> }
> rcu_read_unlock();
> mutex_unlock(&freezer_mutex);
> + cpus_read_unlock();
> }
>
> static ssize_t freezer_write(struct kernfs_open_file *of,
This was reported here as well
https://lore.kernel.org/lkml/90147a2b-982e-ae57-9b7c-062bee0fab07-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org/
Reviewed-by: Mukesh Ojha <quic_mojha-jfJNa2p1gH1BDgjK7y7TUQ@public.gmane.org>
--Mukesh
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] cgroup,freezer: hold cpu_hotplug_lock before freezer_mutex
[not found] ` <695b8d1c-6b7a-91b1-6941-c459cab038b0-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
2023-04-05 13:28 ` Peter Zijlstra
2023-04-05 13:57 ` Mukesh Ojha
@ 2023-04-12 17:31 ` Tejun Heo
2 siblings, 0 replies; 5+ messages in thread
From: Tejun Heo @ 2023-04-12 17:31 UTC (permalink / raw)
To: Tetsuo Handa
Cc: Peter Zijlstra, Ingo Molnar, Rafael J. Wysocki, Zefan Li,
Johannes Weiner, Cgroups, syzbot, syzkaller-bugs, Hillf Danton
On Wed, Apr 05, 2023 at 10:15:32PM +0900, Tetsuo Handa wrote:
> syzbot is reporting circular locking dependency between cpu_hotplug_lock
> and freezer_mutex, for commit f5d39b020809 ("freezer,sched: Rewrite core
> freezer logic") replaced atomic_inc() in freezer_apply_state() with
> static_branch_inc() which holds cpu_hotplug_lock.
>
> cpu_hotplug_lock => cgroup_threadgroup_rwsem => freezer_mutex
>
> cgroup_file_write() {
> cgroup_procs_write() {
> __cgroup_procs_write() {
> cgroup_procs_write_start() {
> cgroup_attach_lock() {
> cpus_read_lock() {
> percpu_down_read(&cpu_hotplug_lock);
> }
> percpu_down_write(&cgroup_threadgroup_rwsem);
> }
> }
> cgroup_attach_task() {
> cgroup_migrate() {
> cgroup_migrate_execute() {
> freezer_attach() {
> mutex_lock(&freezer_mutex);
> (...snipped...)
> }
> }
> }
> }
> (...snipped...)
> }
> }
> }
>
> freezer_mutex => cpu_hotplug_lock
>
> cgroup_file_write() {
> freezer_write() {
> freezer_change_state() {
> mutex_lock(&freezer_mutex);
> freezer_apply_state() {
> static_branch_inc(&freezer_active) {
> static_key_slow_inc() {
> cpus_read_lock();
> static_key_slow_inc_cpuslocked();
> cpus_read_unlock();
> }
> }
> }
> mutex_unlock(&freezer_mutex);
> }
> }
> }
>
> Swap locking order by moving cpus_read_lock() in freezer_apply_state()
> to before mutex_lock(&freezer_mutex) in freezer_change_state().
>
> Reported-by: syzbot <syzbot+c39682e86c9d84152f93-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
> Link: https://syzkaller.appspot.com/bug?extid=c39682e86c9d84152f93
> Suggested-by: Hillf Danton <hdanton-k+cT0dCbe1g@public.gmane.org>
> Fixes: f5d39b020809 ("freezer,sched: Rewrite core freezer logic")
> Signed-off-by: Tetsuo Handa <penguin-kernel-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
Applied to cgroup/for-6.3-fixes.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-04-12 17:31 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-11-02 10:36 [syzbot] possible deadlock in static_key_slow_inc (2) syzbot
[not found] ` <00000000000009483d05ec7a6b93-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2023-04-05 13:15 ` [PATCH] cgroup,freezer: hold cpu_hotplug_lock before freezer_mutex Tetsuo Handa
[not found] ` <695b8d1c-6b7a-91b1-6941-c459cab038b0-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
2023-04-05 13:28 ` Peter Zijlstra
2023-04-05 13:57 ` Mukesh Ojha
2023-04-12 17:31 ` Tejun Heo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).