======================================================
WARNING: possible circular locking dependency detected
5.19.0-syzkaller #0 Not tainted
------------------------------------------------------
kswapd1/129 is trying to acquire lock:
ffff888044648990 (jbd2_handle){++++}-{0:0}, at: start_this_handle+0xfb4/0x14a0 fs/jbd2/transaction.c:461

but task is already holding lock:
ffffffff8beb9500 (fs_reclaim){+.+.}-{0:0}, at: try_to_freeze_unsafe include/linux/freezer.h:58 [inline]
ffffffff8beb9500 (fs_reclaim){+.+.}-{0:0}, at: try_to_freeze include/linux/freezer.h:67 [inline]
ffffffff8beb9500 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat+0xd1e/0x1570 mm/vmscan.c:4229

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (fs_reclaim){+.+.}-{0:0}:
       __fs_reclaim_acquire mm/page_alloc.c:4593 [inline]
       fs_reclaim_acquire+0x115/0x160 mm/page_alloc.c:4607
       might_alloc include/linux/sched/mm.h:271 [inline]
       slab_pre_alloc_hook mm/slab.h:723 [inline]
       slab_alloc_node mm/slab.c:3200 [inline]
       kmem_cache_alloc_node_trace+0x48/0x5b0 mm/slab.c:3611
       kmalloc_node include/linux/slab.h:618 [inline]
       kzalloc_node include/linux/slab.h:744 [inline]
       mempool_create_node mm/mempool.c:266 [inline]
       mempool_create+0x4e/0xc0 mm/mempool.c:255
       mempool_create_page_pool include/linux/mempool.h:107 [inline]
       fscrypt_initialize+0x86/0xa0 fs/crypto/crypto.c:330
       fscrypt_setup_encryption_info+0xef/0xe90 fs/crypto/keysetup.c:531
       fscrypt_get_encryption_info+0x34a/0x3f0 fs/crypto/keysetup.c:640
       fscrypt_setup_filename+0x238/0xec0 fs/crypto/fname.c:433
       __fscrypt_prepare_lookup+0x28/0xf0 fs/crypto/hooks.c:102
       fscrypt_prepare_lookup include/linux/fscrypt.h:947 [inline]
       ext4_fname_prepare_lookup+0x1ba/0x200 fs/ext4/crypto.c:46
       ext4_lookup_entry fs/ext4/namei.c:1717 [inline]
       ext4_lookup fs/ext4/namei.c:1792 [inline]
       ext4_lookup+0x12d/0x700 fs/ext4/namei.c:1783
       __lookup_hash+0x117/0x180 fs/namei.c:1602
       do_rmdir+0x22c/0x430 fs/namei.c:4110
       __do_sys_rmdir fs/namei.c:4141 [inline]
       __se_sys_rmdir fs/namei.c:4139 [inline]
       __x64_sys_rmdir+0xc6/0x110 fs/namei.c:4139
       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 (fscrypt_init_mutex){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x12f/0x1350 kernel/locking/mutex.c:747
       fscrypt_initialize+0x3c/0xa0 fs/crypto/crypto.c:324
       fscrypt_setup_encryption_info+0xef/0xe90 fs/crypto/keysetup.c:531
       fscrypt_get_encryption_info+0x34a/0x3f0 fs/crypto/keysetup.c:640
       fscrypt_setup_filename+0x238/0xec0 fs/crypto/fname.c:433
       ext4_fname_setup_filename+0x88/0x110 fs/ext4/crypto.c:28
       ext4_add_entry+0x3aa/0xe30 fs/ext4/namei.c:2344
       ext4_rename+0x190a/0x2650 fs/ext4/namei.c:3864
       ext4_rename2+0x1c2/0x270 fs/ext4/namei.c:4144
       vfs_rename+0xef2/0x17a0 fs/namei.c:4719
       do_renameat2+0xb5e/0xc80 fs/namei.c:4870
       __do_sys_renameat2 fs/namei.c:4903 [inline]
       __se_sys_renameat2 fs/namei.c:4900 [inline]
       __x64_sys_renameat2+0xe4/0x120 fs/namei.c:4900
       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 (jbd2_handle){++++}-{0:0}:
       check_prev_add kernel/locking/lockdep.c:3095 [inline]
       check_prevs_add kernel/locking/lockdep.c:3214 [inline]
       validate_chain kernel/locking/lockdep.c:3829 [inline]
       __lock_acquire+0x2abe/0x5660 kernel/locking/lockdep.c:5053
       lock_acquire kernel/locking/lockdep.c:5665 [inline]
       lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5630
       start_this_handle+0xfe7/0x14a0 fs/jbd2/transaction.c:463
       jbd2__journal_start+0x399/0x930 fs/jbd2/transaction.c:520
       __ext4_journal_start_sb+0x3a8/0x4a0 fs/ext4/ext4_jbd2.c:105
       __ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline]
       ext4_dirty_inode+0x9d/0x110 fs/ext4/inode.c:5949
       __mark_inode_dirty+0x495/0x1050 fs/fs-writeback.c:2381
       mark_inode_dirty_sync include/linux/fs.h:2337 [inline]
       iput.part.0+0x57/0x820 fs/inode.c:1767
       iput+0x58/0x70 fs/inode.c:1760
       dentry_unlink_inode+0x2b1/0x460 fs/dcache.c:401
       __dentry_kill+0x3c0/0x640 fs/dcache.c:607
       shrink_dentry_list+0x23c/0x800 fs/dcache.c:1201
       prune_dcache_sb+0xe7/0x140 fs/dcache.c:1282
       super_cache_scan+0x336/0x590 fs/super.c:104
       do_shrink_slab+0x42d/0xbd0 mm/vmscan.c:770
       shrink_slab+0x17c/0x6f0 mm/vmscan.c:930
       shrink_node_memcgs mm/vmscan.c:3124 [inline]
       shrink_node+0x8b3/0x1db0 mm/vmscan.c:3245
       kswapd_shrink_node mm/vmscan.c:4024 [inline]
       balance_pgdat+0x8ef/0x1570 mm/vmscan.c:4215
       kswapd+0x7a5/0xf80 mm/vmscan.c:4475
       kthread+0x2e9/0x3a0 kernel/kthread.c:376
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306

other info that might help us debug this:

Chain exists of:
  jbd2_handle --> fscrypt_init_mutex --> fs_reclaim

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(fs_reclaim);
                               lock(fscrypt_init_mutex);
                               lock(fs_reclaim);
  lock(jbd2_handle);

 *** DEADLOCK ***

3 locks held by kswapd1/129:
 #0: ffffffff8beb9500 (fs_reclaim){+.+.}-{0:0}, at: try_to_freeze_unsafe include/linux/freezer.h:58 [inline]
 #0: ffffffff8beb9500 (fs_reclaim){+.+.}-{0:0}, at: try_to_freeze include/linux/freezer.h:67 [inline]
 #0: ffffffff8beb9500 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat+0xd1e/0x1570 mm/vmscan.c:4229
 #1: ffffffff8be79270 (shrinker_rwsem){++++}-{3:3}, at: shrink_slab+0xc9/0x6f0 mm/vmscan.c:920
 #2: ffff88801b30c0e0 (&type->s_umount_key#52){++++}-{3:3}, at: trylock_super fs/super.c:415 [inline]
 #2: ffff88801b30c0e0 (&type->s_umount_key#52){++++}-{3:3}, at: super_cache_scan+0x6c/0x590 fs/super.c:79

stack backtrace:
CPU: 2 PID: 129 Comm: kswapd1 Not tainted 5.19.0-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
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:2175
 check_prev_add kernel/locking/lockdep.c:3095 [inline]
 check_prevs_add kernel/locking/lockdep.c:3214 [inline]
 validate_chain kernel/locking/lockdep.c:3829 [inline]
 __lock_acquire+0x2abe/0x5660 kernel/locking/lockdep.c:5053
 lock_acquire kernel/locking/lockdep.c:5665 [inline]
 lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5630
 start_this_handle+0xfe7/0x14a0 fs/jbd2/transaction.c:463
 jbd2__journal_start+0x399/0x930 fs/jbd2/transaction.c:520
 __ext4_journal_start_sb+0x3a8/0x4a0 fs/ext4/ext4_jbd2.c:105
 __ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline]
 ext4_dirty_inode+0x9d/0x110 fs/ext4/inode.c:5949
 __mark_inode_dirty+0x495/0x1050 fs/fs-writeback.c:2381
 mark_inode_dirty_sync include/linux/fs.h:2337 [inline]
 iput.part.0+0x57/0x820 fs/inode.c:1767
 iput+0x58/0x70 fs/inode.c:1760
 dentry_unlink_inode+0x2b1/0x460 fs/dcache.c:401
 __dentry_kill+0x3c0/0x640 fs/dcache.c:607
 shrink_dentry_list+0x23c/0x800 fs/dcache.c:1201
 prune_dcache_sb+0xe7/0x140 fs/dcache.c:1282
 super_cache_scan+0x336/0x590 fs/super.c:104
 do_shrink_slab+0x42d/0xbd0 mm/vmscan.c:770
 shrink_slab+0x17c/0x6f0 mm/vmscan.c:930
 shrink_node_memcgs mm/vmscan.c:3124 [inline]
 shrink_node+0x8b3/0x1db0 mm/vmscan.c:3245
 kswapd_shrink_node mm/vmscan.c:4024 [inline]
 balance_pgdat+0x8ef/0x1570 mm/vmscan.c:4215
 kswapd+0x7a5/0xf80 mm/vmscan.c:4475
 kthread+0x2e9/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>