======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     Y
------------------------------------------------------
kworker/1:0/24 is trying to acquire lock:
ffff88816ab05c38 (kn->active#117){++++}-{0:0}, at: __kernfs_remove+0x493/0x910

but task is already holding lock:
ffffc900001e7c40 ((work_completion)(&mddev->del_work)){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #4 ((work_completion)(&mddev->del_work)){+.+.}-{0:0}:
       process_scheduled_works+0xc03/0x1630
       worker_thread+0xa47/0xfb0
       kthread+0x38b/0x480
       ret_from_fork+0x514/0xb70
       ret_from_fork_asm+0x1a/0x30

-> #3 ((wq_completion)md_misc){+.+.}-{0:0}:
       touch_wq_lockdep_map+0xcb/0x180
       __flush_workqueue+0x148/0x10b0
       md_alloc+0x32/0xf20
       md_alloc_and_put+0x1a/0x1f0
       blk_request_module+0x27d/0x2a0
       blkdev_get_no_open+0x3f/0xe0
       bdev_file_open_by_dev+0xa0/0x240
       swsusp_check+0x56/0x490
       software_resume+0x51/0x4c0
       resume_store+0x342/0x500
       kernfs_fop_write_iter+0x3a4/0x540
       vfs_write+0x612/0xba0
       ksys_write+0x150/0x270
       do_syscall_64+0x166/0x520
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #2 (major_names_lock){+.+.}-{4:4}:
       __mutex_lock+0x197/0x15a0
       blk_request_module+0x35/0x2a0
       blkdev_get_no_open+0x3f/0xe0
       bdev_file_open_by_dev+0xa0/0x240
       md_import_device+0x2e9/0x650
       new_dev_store+0x46d/0x860
       md_attr_store+0x3b7/0x640
       kernfs_fop_write_iter+0x3a4/0x540
       vfs_write+0x612/0xba0
       ksys_write+0x150/0x270
       do_syscall_64+0x166/0x520
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 (&mddev->reconfig_mutex){+.+.}-{4:4}:
       __mutex_lock+0x197/0x15a0
       array_state_store+0x4a5/0xe90
       md_attr_store+0x3b7/0x640
       kernfs_fop_write_iter+0x3a4/0x540
       vfs_write+0x612/0xba0
       ksys_write+0x150/0x270
       do_syscall_64+0x166/0x520
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (kn->active#117){++++}-{0:0}:
       __lock_acquire+0x164c/0x2de0
       lock_acquire+0x115/0x350
       kernfs_drain+0x293/0x640
       __kernfs_remove+0x493/0x910
       kernfs_remove_by_name_ns+0xc0/0x140
       sysfs_remove_group+0x101/0x2e0
       sysfs_remove_groups+0x54/0xb0
       __kobject_del+0x83/0x310
       kobject_put+0x23a/0x550
       process_scheduled_works+0xc3d/0x1630
       worker_thread+0xa47/0xfb0
       kthread+0x38b/0x480
       ret_from_fork+0x514/0xb70
       ret_from_fork_asm+0x1a/0x30

other info that might help us debug this:

Chain exists of:
  kn->active#117 --> (wq_completion)md_misc --> (work_completion)(&mddev->del_work)

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock((work_completion)(&mddev->del_work));
                               lock((wq_completion)md_misc);
                               lock((work_completion)(&mddev->del_work));
  lock(kn->active#117);

 *** DEADLOCK ***

locks held by kworker/1:0/24: 2, last CPU#1:
 #0: ffff8881076ea148 ((wq_completion)md_misc){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630
 #1: ffffc900001e7c40 ((work_completion)(&mddev->del_work)){+.+.}-{0:0}, at: process_scheduled_works+0x97a/0x1630

stack backtrace:
CPU: 1 UID: 0 PID: 24 Comm: kworker/1:0 Tainted: G             L     Y syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP, [Y]=FORCED_BIND
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: md_misc mddev_delayed_delete
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150
 print_circular_bug+0x2e2/0x300
 check_noncircular+0x12f/0x150
 __lock_acquire+0x164c/0x2de0
 lock_acquire+0x115/0x350
 kernfs_drain+0x293/0x640
 __kernfs_remove+0x493/0x910
 kernfs_remove_by_name_ns+0xc0/0x140
 sysfs_remove_group+0x101/0x2e0
 sysfs_remove_groups+0x54/0xb0
 __kobject_del+0x83/0x310
 kobject_put+0x23a/0x550
 process_scheduled_works+0xc3d/0x1630
 worker_thread+0xa47/0xfb0
 kthread+0x38b/0x480
 ret_from_fork+0x514/0xb70
 ret_from_fork_asm+0x1a/0x30
 </TASK>
