REISERFS (device loop5): journal params: device loop5, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop5): checking transaction log (loop5) REISERFS (device loop5): Using r5 hash to sort names REISERFS (device loop5): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 4.19.211-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/11651 is trying to acquire lock: 00000000cc6d2198 (&journal->j_mutex){+.+.}, at: reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:816 [inline] 00000000cc6d2198 (&journal->j_mutex){+.+.}, at: lock_journal fs/reiserfs/journal.c:538 [inline] 00000000cc6d2198 (&journal->j_mutex){+.+.}, at: do_journal_begin_r+0x298/0x10b0 fs/reiserfs/journal.c:3057 but task is already holding lock: 00000000ec0e4cae (sb_writers#15){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] 00000000ec0e4cae (sb_writers#15){.+.+}, at: mnt_want_write_file+0x63/0x1d0 fs/namespace.c:418 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_writers#15){.+.+}: sb_start_write include/linux/fs.h:1579 [inline] mnt_want_write_file+0x63/0x1d0 fs/namespace.c:418 reiserfs_ioctl+0x1a7/0x9a0 fs/reiserfs/ioctl.c:110 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:501 [inline] do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705 __do_sys_ioctl fs/ioctl.c:712 [inline] __se_sys_ioctl fs/ioctl.c:710 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #1 (&sbi->lock){+.+.}: reiserfs_write_lock_nested+0x65/0xe0 fs/reiserfs/lock.c:78 reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:817 [inline] lock_journal fs/reiserfs/journal.c:538 [inline] do_journal_begin_r+0x2a2/0x10b0 fs/reiserfs/journal.c:3057 journal_begin+0x162/0x400 fs/reiserfs/journal.c:3265 reiserfs_fill_super+0x1a81/0x2d80 fs/reiserfs/super.c:2117 mount_bdev+0x2fc/0x3b0 fs/super.c:1158 mount_fs+0xa3/0x310 fs/super.c:1261 vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961 vfs_kern_mount fs/namespace.c:951 [inline] do_new_mount fs/namespace.c:2492 [inline] do_mount+0x115c/0x2f50 fs/namespace.c:2822 ksys_mount+0xcf/0x130 fs/namespace.c:3038 __do_sys_mount fs/namespace.c:3052 [inline] __se_sys_mount fs/namespace.c:3049 [inline] __x64_sys_mount+0xba/0x150 fs/namespace.c:3049 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe -> #0 (&journal->j_mutex){+.+.}: __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:816 [inline] lock_journal fs/reiserfs/journal.c:538 [inline] do_journal_begin_r+0x298/0x10b0 fs/reiserfs/journal.c:3057 journal_begin+0x162/0x400 fs/reiserfs/journal.c:3265 reiserfs_dirty_inode+0xff/0x250 fs/reiserfs/super.c:716 __mark_inode_dirty+0x16b/0x1140 fs/fs-writeback.c:2164 mark_inode_dirty include/linux/fs.h:2086 [inline] reiserfs_ioctl+0x7dc/0x9a0 fs/reiserfs/ioctl.c:118 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:501 [inline] do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705 __do_sys_ioctl fs/ioctl.c:712 [inline] __se_sys_ioctl fs/ioctl.c:710 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe other info that might help us debug this: Chain exists of: &journal->j_mutex --> &sbi->lock --> sb_writers#15 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_writers#15); lock(&sbi->lock); lock(sb_writers#15); lock(&journal->j_mutex); *** DEADLOCK *** 1 lock held by syz-executor.5/11651: #0: 00000000ec0e4cae (sb_writers#15){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline] #0: 00000000ec0e4cae (sb_writers#15){.+.+}, at: mnt_want_write_file+0x63/0x1d0 fs/namespace.c:418 stack backtrace: CPU: 1 PID: 11651 Comm: syz-executor.5 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_circular_bug.constprop.0.cold+0x2d7/0x41e kernel/locking/lockdep.c:1222 check_prev_add kernel/locking/lockdep.c:1866 [inline] check_prevs_add kernel/locking/lockdep.c:1979 [inline] validate_chain kernel/locking/lockdep.c:2420 [inline] __lock_acquire+0x30c9/0x3ff0 kernel/locking/lockdep.c:3416 lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908 __mutex_lock_common kernel/locking/mutex.c:937 [inline] __mutex_lock+0xd7/0x1190 kernel/locking/mutex.c:1078 reiserfs_mutex_lock_safe fs/reiserfs/reiserfs.h:816 [inline] lock_journal fs/reiserfs/journal.c:538 [inline] do_journal_begin_r+0x298/0x10b0 fs/reiserfs/journal.c:3057 journal_begin+0x162/0x400 fs/reiserfs/journal.c:3265 reiserfs_dirty_inode+0xff/0x250 fs/reiserfs/super.c:716 __mark_inode_dirty+0x16b/0x1140 fs/fs-writeback.c:2164 mark_inode_dirty include/linux/fs.h:2086 [inline] reiserfs_ioctl+0x7dc/0x9a0 fs/reiserfs/ioctl.c:118 vfs_ioctl fs/ioctl.c:46 [inline] file_ioctl fs/ioctl.c:501 [inline] do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688 ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705 __do_sys_ioctl fs/ioctl.c:712 [inline] __se_sys_ioctl fs/ioctl.c:710 [inline] __x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7f33f2a8c0d9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f33f0ffe168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f33f2babf80 RCX: 00007f33f2a8c0d9 RDX: 0000000020000040 RSI: 0000000040087602 RDI: 0000000000000003 RBP: 00007f33f2ae7ae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffd04c1365f R14: 00007f33f0ffe300 R15: 0000000000022000 REISERFS (device loop5): found reiserfs format "3.6" with non-standard journal REISERFS (device loop5): using ordered data mode reiserfs: using flush barriers REISERFS (device loop5): journal params: device loop5, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop5): checking transaction log (loop5) REISERFS (device loop5): Using r5 hash to sort names REISERFS (device loop5): Created .reiserfs_priv - reserved for xattr storage. REISERFS (device loop5): found reiserfs format "3.6" with non-standard journal REISERFS (device loop5): using ordered data mode reiserfs: using flush barriers REISERFS (device loop5): journal params: device loop5, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop5): checking transaction log (loop5) REISERFS (device loop5): Using r5 hash to sort names REISERFS (device loop5): Created .reiserfs_priv - reserved for xattr storage. ieee802154 phy0 wpan0: encryption failed: -22 ieee802154 phy1 wpan1: encryption failed: -22 REISERFS (device loop5): found reiserfs format "3.6" with non-standard journal REISERFS (device loop5): using ordered data mode reiserfs: using flush barriers REISERFS (device loop5): journal params: device loop5, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30 REISERFS (device loop5): checking transaction log (loop5) REISERFS (device loop5): Using r5 hash to sort names REISERFS (device loop5): Created .reiserfs_priv - reserved for xattr storage. L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. wlan0: mtu less than device minimum netlink: 20 bytes leftover after parsing attributes in process `syz-executor.2'. netlink: 12 bytes leftover after parsing attributes in process `syz-executor.1'. netlink: 7 bytes leftover after parsing attributes in process `syz-executor.1'. netlink: 'syz-executor.0': attribute type 1 has an invalid length. EXT4-fs error (device loop4): ext4_orphan_get:1256: comm syz-executor.4: bad orphan inode 34020 EXT4-fs (loop4): mounted filesystem without journal. Opts: ,errors=continue list_del corruption, ffff888047bbfa90->next is LIST_POISON1 (dead000000000100) ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:45! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 0 PID: 12368 Comm: syz-executor.1 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 RIP: 0010:__list_del_entry_valid.cold+0x23/0x4a lib/list_debug.c:45 Code: e8 11 43 f7 ff 0f 0b 48 89 ee 48 c7 c7 40 e4 b3 88 e8 00 43 f7 ff 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 80 e3 b3 88 e8 ec 42 f7 ff <0f> 0b 4c 89 e2 48 89 ee 48 c7 c7 e0 e3 b3 88 e8 d8 42 f7 ff 0f 0b RSP: 0018:ffff888047bbf970 EFLAGS: 00010086 RAX: 000000000000004e RBX: ffff888047bbfa78 RCX: 0000000000000000 RDX: 0000000000040000 RSI: ffffffff814dff01 RDI: ffffed1008f77f20 RBP: ffff888047bbfa90 R08: 000000000000004e R09: 0000000000000000 R10: 0000000000000005 R11: ffffffff8c66501b R12: dead000000000200 R13: dead000000000100 R14: ffff888047bbfa98 R15: 0000000000000007 FS: 00007f5d32b72700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000558107c30a38 CR3: 00000000afc07000 CR4: 00000000003406f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600 Call Trace: __list_del_entry include/linux/list.h:117 [inline] list_del include/linux/list.h:125 [inline] __remove_wait_queue include/linux/wait.h:184 [inline] remove_wait_queue+0x2c/0x180 kernel/sched/wait.c:44 __tipc_sendstream+0x373/0x9d0 net/tipc/socket.c:1449 tipc_sendstream+0x4c/0x70 net/tipc/socket.c:1414 sock_sendmsg_nosec net/socket.c:651 [inline] sock_sendmsg+0xc3/0x120 net/socket.c:661 sock_write_iter+0x287/0x3c0 net/socket.c:966 call_write_iter include/linux/fs.h:1821 [inline] new_sync_write fs/read_write.c:474 [inline] __vfs_write+0x51b/0x770 fs/read_write.c:487 vfs_write+0x1f3/0x540 fs/read_write.c:549 ksys_write+0x12b/0x2a0 fs/read_write.c:599 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7f5d346000d9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f5d32b72168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f5d3471ff80 RCX: 00007f5d346000d9 RDX: 000000002000011a RSI: 0000000020000080 RDI: 0000000000000003 RBP: 00007f5d3465bae9 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffef351cd8f R14: 00007f5d32b72300 R15: 0000000000022000 Modules linked in: ---[ end trace fc117ea19488c99a ]--- RIP: 0010:__list_del_entry_valid.cold+0x23/0x4a lib/list_debug.c:45 Code: e8 11 43 f7 ff 0f 0b 48 89 ee 48 c7 c7 40 e4 b3 88 e8 00 43 f7 ff 0f 0b 4c 89 ea 48 89 ee 48 c7 c7 80 e3 b3 88 e8 ec 42 f7 ff <0f> 0b 4c 89 e2 48 89 ee 48 c7 c7 e0 e3 b3 88 e8 d8 42 f7 ff 0f 0b RSP: 0018:ffff888047bbf970 EFLAGS: 00010086 RAX: 000000000000004e RBX: ffff888047bbfa78 RCX: 0000000000000000 RDX: 0000000000040000 RSI: ffffffff814dff01 RDI: ffffed1008f77f20 RBP: ffff888047bbfa90 R08: 000000000000004e R09: 0000000000000000 R10: 0000000000000005 R11: ffffffff8c66501b R12: dead000000000200 R13: dead000000000100 R14: ffff888047bbfa98 R15: 0000000000000007 FS: 00007f5d32b72700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000558107c30a38 CR3: 00000000afc07000 CR4: 00000000003406f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600