loop2: detected capacity change from 0 to 264192
======================================================
WARNING: possible circular locking dependency detected
6.2.0-rc1-next-20221226 #1 Not tainted
------------------------------------------------------
syz-executor.3/9674 is trying to acquire lock:
ffff88800ff9a170 (&journal->j_barrier){+.+.}-{3:3}, at: jbd2_journal_lock_updates+0x162/0x310
but task is already holding lock:
ffff88800ff98b90 (&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:
-> #3 (&sbi->s_writepages_rwsem){++++}-{0:0}:
ext4_writepages+0x1a9/0x5b0
do_writepages+0x1b4/0x6a0
filemap_fdatawrite_wbc+0x14b/0x1b0
__filemap_fdatawrite_range+0xba/0x100
filemap_write_and_wait_range+0xa5/0x130
__iomap_dio_rw+0x5ea/0x1bd0
iomap_dio_rw+0x40/0xa0
ext4_file_read_iter+0x2f4/0x4a0
generic_file_splice_read+0x18b/0x4d0
do_splice_to+0x1bc/0x240
splice_direct_to_actor+0x2b0/0x8c0
do_splice_direct+0x1bc/0x290
do_sendfile+0xb1d/0x1280
__x64_sys_sendfile64+0x1d5/0x210
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+0x9db/0x43b0
__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+0x9db/0x43b0
__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.part.0+0x11e/0x340
__mutex_lock+0x136/0x14e0
jbd2_journal_lock_updates+0x162/0x310
ext4_change_inode_journal_flag+0x187/0x550
ext4_fileattr_set+0x14fa/0x19f0
vfs_fileattr_set+0x780/0xb90
do_vfs_ioctl+0xfa6/0x15d0
__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 --> &sb->s_type->i_mutex_key#6 --> &sbi->s_writepages_rwsem
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&sbi->s_writepages_rwsem);
lock(&sb->s_type->i_mutex_key#6);
lock(&sbi->s_writepages_rwsem);
lock(&journal->j_barrier);
*** DEADLOCK ***
4 locks held by syz-executor.3/9674:
#0: ffff88800ff86438 (sb_writers#3){.+.+}-{0:0}, at: do_vfs_ioctl+0xf6b/0x15d0
#1: ffff88801c15b5b0 (&sb->s_type->i_mutex_key#6){++++}-{3:3}, at: vfs_fileattr_set+0x14c/0xb90
#2: ffff88801c15b750 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_change_inode_journal_flag+0x126/0x550
#3: ffff88800ff98b90 (&sbi->s_writepages_rwsem){++++}-{0:0}, at: ext4_change_inode_journal_flag+0x17f/0x550
stack backtrace:
CPU: 1 PID: 9674 Comm: syz-executor.3 Not tainted 6.2.0-rc1-next-20221226 #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.part.0+0x11e/0x340
__mutex_lock+0x136/0x14e0
jbd2_journal_lock_updates+0x162/0x310
ext4_change_inode_journal_flag+0x187/0x550
ext4_fileattr_set+0x14fa/0x19f0
vfs_fileattr_set+0x780/0xb90
do_vfs_ioctl+0xfa6/0x15d0
__x64_sys_ioctl+0x110/0x210
do_syscall_64+0x3f/0x90
entry_SYSCALL_64_after_hwframe+0x72/0xdc
RIP: 0033:0x7f7ba7b05b19
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:00007f7ba507b188 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f7ba7c18f60 RCX: 00007f7ba7b05b19
RDX: 0000000020000040 RSI: 0000000040086602 RDI: 0000000000000003
RBP: 00007f7ba7b5ff6d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffeb725958f R14: 00007f7ba507b300 R15: 0000000000022000
ISO 9660 Extensions: Microsoft Joliet Level 0
isofs_fill_super: root inode is not a directory. Corrupted media?
loop2: detected capacity change from 0 to 264192
ISO 9660 Extensions: Microsoft Joliet Level 0
9p: Unknown access argument 18446744073709551615: -34
isofs_fill_super: root inode is not a directory. Corrupted media?
FAULT_INJECTION: forcing a failure.
name failslab, interval 1, probability 0, space 0, times 0
CPU: 1 PID: 9694 Comm: syz-executor.5 Not tainted 6.2.0-rc1-next-20221226 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Call Trace:
dump_stack_lvl+0x8f/0xb7
should_fail_ex.cold+0x5/0xa
should_failslab+0x9/0x20
kmem_cache_alloc+0x5a/0x410
__kernfs_new_node+0xd4/0x8c0
kernfs_new_node+0x97/0x120
__kernfs_create_file+0x55/0x350
sysfs_add_file_mode_ns+0x21c/0x440
internal_create_group+0x322/0xb20
sysfs_slab_add+0x18e/0x220
__kmem_cache_create+0x461/0x5d0
kmem_cache_create_usercopy+0x201/0x2f0
p9_client_create+0xc89/0x1050
v9fs_session_init+0x1e1/0x1670
v9fs_mount+0xbd/0xbd0
legacy_get_tree+0x109/0x220
vfs_get_tree+0x92/0x300
path_mount+0x1314/0x1e30
__x64_sys_mount+0x286/0x310
do_syscall_64+0x3f/0x90
entry_SYSCALL_64_after_hwframe+0x72/0xdc
RIP: 0033:0x7fce08b8bb19
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:00007fce06101188 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fce08c9ef60 RCX: 00007fce08b8bb19
RDX: 0000000020000080 RSI: 0000000020000180 RDI: 0000000000000000
RBP: 00007fce061011d0 R08: 0000000020000200 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007fffd310014f R14: 00007fce06101300 R15: 0000000000022000
loop2: detected capacity change from 0 to 264192
ISO 9660 Extensions: Microsoft Joliet Level 0
isofs_fill_super: root inode is not a directory. Corrupted media?
loop2: detected capacity change from 0 to 264192
ISO 9660 Extensions: Microsoft Joliet Level 0
isofs_fill_super: root inode is not a directory. Corrupted media?
kmem_cache_create_usercopy(9p-fcall-cache) failed with error -12
CPU: 1 PID: 9694 Comm: syz-executor.5 Not tainted 6.2.0-rc1-next-20221226 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Call Trace:
dump_stack_lvl+0x8f/0xb7
kmem_cache_create_usercopy.cold+0x4c/0x6d
p9_client_create+0xc89/0x1050
v9fs_session_init+0x1e1/0x1670
v9fs_mount+0xbd/0xbd0
legacy_get_tree+0x109/0x220
vfs_get_tree+0x92/0x300
path_mount+0x1314/0x1e30
__x64_sys_mount+0x286/0x310
do_syscall_64+0x3f/0x90
entry_SYSCALL_64_after_hwframe+0x72/0xdc
RIP: 0033:0x7fce08b8bb19
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:00007fce06101188 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fce08c9ef60 RCX: 00007fce08b8bb19
RDX: 0000000020000080 RSI: 0000000020000180 RDI: 0000000000000000
RBP: 00007fce061011d0 R08: 0000000020000200 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007fffd310014f R14: 00007fce06101300 R15: 0000000000022000
9p: Unknown access argument 18446744073709551615: -34