loop5: detected capacity change from 0 to 40 ====================================================== WARNING: possible circular locking dependency detected 6.1.0-rc8-next-20221206 #1 Not tainted ------------------------------------------------------ syz-executor.4/5579 is trying to acquire lock: ffff888010898170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x162/0x310 but task is already holding lock: ffff888010886b90 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_change_inode_journal_flag+0x17f/0x550 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #4 (&sbi->s_writepages_rwsem){++++}-{0:0}: percpu_down_write+0x51/0x350 ext4_change_inode_journal_flag+0x17f/0x550 ext4_fileattr_set+0x14fb/0x19f0 vfs_fileattr_set+0x780/0xb90 do_vfs_ioctl+0xa6c/0x1af0 __x64_sys_ioctl+0x110/0x210 do_syscall_64+0x3f/0x90 entry_SYSCALL_64_after_hwframe+0x72/0xdc -> #3 (mapping.invalidate_lock){++++}-{3:3}: down_write+0x94/0x220 ext4_setattr+0x99d/0x2940 notify_change+0xca5/0x1400 do_truncate+0x143/0x200 do_sys_ftruncate+0x53c/0x720 do_syscall_64+0x3f/0x90 entry_SYSCALL_64_after_hwframe+0x72/0xdc -> #2 (&sb->s_type->i_mutex_key#6){++++}-{3:3}: down_read+0x9c/0x450 ext4_bmap+0x52/0x470 bmap+0xb0/0x130 jbd2_journal_bmap+0xac/0x190 jbd2_journal_flush+0x857/0xc10 __ext4_ioctl+0x9c5/0x4500 __x64_sys_ioctl+0x19e/0x210 do_syscall_64+0x3f/0x90 entry_SYSCALL_64_after_hwframe+0x72/0xdc -> #1 (&journal->j_checkpoint_mutex){+.+.}-{3:3}: mutex_lock_io_nested+0x14c/0x1330 jbd2_journal_flush+0x19e/0xc10 __ext4_ioctl+0x9c5/0x4500 __x64_sys_ioctl+0x19e/0x210 do_syscall_64+0x3f/0x90 entry_SYSCALL_64_after_hwframe+0x72/0xdc -> #0 (&journal->j_barrier){+.+.}-{3:3}: __lock_acquire+0x2a02/0x5e70 lock_acquire+0x1a6/0x530 __mutex_lock+0x136/0x14e0 jbd2_journal_lock_updates+0x162/0x310 ext4_change_inode_journal_flag+0x187/0x550 ext4_fileattr_set+0x14fb/0x19f0 vfs_fileattr_set+0x780/0xb90 do_vfs_ioctl+0xa6c/0x1af0 __x64_sys_ioctl+0x110/0x210 do_syscall_64+0x3f/0x90 entry_SYSCALL_64_after_hwframe+0x72/0xdc other info that might help us debug this: Chain exists of: &journal->j_barrier --> mapping.invalidate_lock --> &sbi->s_writepages_rwsem Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sbi->s_writepages_rwsem); lock(mapping.invalidate_lock); lock(&sbi->s_writepages_rwsem); lock(&journal->j_barrier); *** DEADLOCK *** 4 locks held by syz-executor.4/5579: #0: ffff888010884438 (sb_writers#3){.+.+}-{0:0}, at: do_vfs_ioctl+0xa2f/0x1af0 #1: ffff88801e75bfa0 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: vfs_fileattr_set+0x14c/0xb90 #2: ffff88801e75c140 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_change_inode_journal_flag+0x126/0x550 #3: ffff888010886b90 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_change_inode_journal_flag+0x17f/0x550 stack backtrace: CPU: 0 PID: 5579 Comm: syz-executor.4 Not tainted 6.1.0-rc8-next-20221206 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Call Trace: dump_stack_lvl+0x8f/0xb7 check_noncircular+0x263/0x2e0 __lock_acquire+0x2a02/0x5e70 lock_acquire+0x1a6/0x530 __mutex_lock+0x136/0x14e0 jbd2_journal_lock_updates+0x162/0x310 ext4_change_inode_journal_flag+0x187/0x550 ext4_fileattr_set+0x14fb/0x19f0 vfs_fileattr_set+0x780/0xb90 do_vfs_ioctl+0xa6c/0x1af0 __x64_sys_ioctl+0x110/0x210 do_syscall_64+0x3f/0x90 entry_SYSCALL_64_after_hwframe+0x72/0xdc RIP: 0033:0x7f974bf19b19 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f974948f188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f974c02cf60 RCX: 00007f974bf19b19 RDX: 0000000020001780 RSI: 0000000040086602 RDI: 0000000000000003 RBP: 00007f974bf73f6d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffe728ffe4f R14: 00007f974948f300 R15: 0000000000022000 loop4: detected capacity change from 0 to 40 loop6: detected capacity change from 0 to 40 syz-executor.6: attempt to access beyond end of device loop6: rw=2049, sector=124, nr_sectors = 4 limit=40 Buffer I/O error on dev loop6, logical block 31, lost async page write kworker/u4:5: attempt to access beyond end of device loop4: rw=1, sector=124, nr_sectors = 4 limit=40 Buffer I/O error on dev loop4, logical block 31, lost async page write loop4: detected capacity change from 0 to 40 loop6: detected capacity change from 0 to 40 syz-executor.6: attempt to access beyond end of device loop6: rw=2049, sector=124, nr_sectors = 4 limit=40 Buffer I/O error on dev loop6, logical block 31, lost async page write kworker/u4:2: attempt to access beyond end of device loop4: rw=1, sector=124, nr_sectors = 4 limit=40 Buffer I/O error on dev loop4, logical block 31, lost async page write loop6: detected capacity change from 0 to 40 loop4: detected capacity change from 0 to 40 syz-executor.6: attempt to access beyond end of device loop6: rw=2049, sector=124, nr_sectors = 4 limit=40 Buffer I/O error on dev loop6, logical block 31, lost async page write kworker/u4:4: attempt to access beyond end of device loop4: rw=1, sector=124, nr_sectors = 4 limit=40 Buffer I/O error on dev loop4, logical block 31, lost async page write loop4: detected capacity change from 0 to 40 loop6: detected capacity change from 0 to 40 syz-executor.6: attempt to access beyond end of device loop6: rw=2049, sector=124, nr_sectors = 4 limit=40 Buffer I/O error on dev loop6, logical block 31, lost async page write kworker/u4:5: attempt to access beyond end of device loop4: rw=1, sector=124, nr_sectors = 4 limit=40 Buffer I/O error on dev loop4, logical block 31, lost async page write loop6: detected capacity change from 0 to 40 loop7: detected capacity change from 0 to 40 loop5: detected capacity change from 0 to 40 loop6: detected capacity change from 0 to 40 loop5: detected capacity change from 0 to 40 loop7: detected capacity change from 0 to 40 loop6: detected capacity change from 0 to 40 syz-executor.1 (5740) used greatest stack depth: 23832 bytes left loop5: detected capacity change from 0 to 40 netlink: 4 bytes leftover after parsing attributes in process `syz-executor.0'. netlink: 4 bytes leftover after parsing attributes in process `syz-executor.0'. audit: type=1400 audit(1670327045.794:10): avc: denied { block_suspend } for pid=5909 comm="syz-executor.2" capability=36 scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=capability2 permissive=1 syz-executor.5 (5907) used greatest stack depth: 23576 bytes left Process accounting resumed Process accounting resumed netlink: 4 bytes leftover after parsing attributes in process `syz-executor.7'. netlink: 'syz-executor.7': attribute type 1 has an invalid length. netlink: 4 bytes leftover after parsing attributes in process `syz-executor.7'. Process accounting resumed Process accounting resumed