linux-kernel - Re: [syzbot] [cgroups?] possible deadlock in console_lock_spinning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250122103542.1719-1-hdanton@sina.com>
Date: Wed, 22 Jan 2025 18:35:40 +0800
From: Hillf Danton <hdanton@...a.com>
To: syzbot <syzbot+622acb507894a48b2ce9@...kaller.appspotmail.com>
Cc: linux-kernel@...r.kernel.org,
	syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [cgroups?] possible deadlock in console_lock_spinning_enable (5)

On Thu, 03 Oct 2024 13:37:23 -0700
> syzbot has found a reproducer for the following issue on:
> 
> HEAD commit:    5f5673607153 Merge branch 'for-next/core' into for-kernelci
> git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17f0f580580000

#syz test upstream  master

--- x/kernel/workqueue.c
+++ y/kernel/workqueue.c
@@ -7815,7 +7815,7 @@ void __init workqueue_init_early(void)
 
 	system_wq = alloc_workqueue("events", 0, 0);
 	system_highpri_wq = alloc_workqueue("events_highpri", WQ_HIGHPRI, 0);
-	system_long_wq = alloc_workqueue("events_long", 0, 0);
+	system_long_wq = alloc_workqueue("events_long", WQ_MEM_RECLAIM, 0);
 	system_unbound_wq = alloc_workqueue("events_unbound", WQ_UNBOUND,
 					    WQ_MAX_ACTIVE);
 	system_freezable_wq = alloc_workqueue("events_freezable",
--