ci2 starts bisection 2023-02-28 05:52:11.845787744 +0000 UTC m=+31018.917748222 bisecting fixing commit since 2bca25eaeba6190efbfcb38ed169bd7ee43b5aaf building syzkaller on 2c6543adc4c5a9108455d1e59b0df0d4afc05c99 ensuring issue is reproducible on original commit 2bca25eaeba6190efbfcb38ed169bd7ee43b5aaf testing commit 2bca25eaeba6190efbfcb38ed169bd7ee43b5aaf gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 027ccce65f93e2ee173de18ea2635eca9dd4151af607b43c526a5376d92378bc run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: exit status NUM run #1: crashed: possible deadlock in mnt_want_write_file run #2: crashed: possible deadlock in mnt_want_write_file run #3: crashed: possible deadlock in mnt_want_write_file run #4: crashed: possible deadlock in chown_common run #5: crashed: possible deadlock in mnt_want_write_file run #6: crashed: possible deadlock in mnt_want_write_file run #7: crashed: possible deadlock in mnt_want_write_file run #8: crashed: possible deadlock in mnt_want_write_file run #9: crashed: possible deadlock in mnt_want_write_file run #10: crashed: possible deadlock in mnt_want_write_file run #11: crashed: possible deadlock in mnt_want_write_file run #12: crashed: possible deadlock in mnt_want_write_file run #13: crashed: possible deadlock in mnt_want_write_file run #14: crashed: possible deadlock in chown_common run #15: crashed: possible deadlock in mnt_want_write_file run #16: crashed: possible deadlock in mnt_want_write_file run #17: crashed: possible deadlock in mnt_want_write_file run #18: crashed: possible deadlock in chown_common run #19: crashed: possible deadlock in mnt_want_write_file testing current HEAD ae3419fbac845b4d3f3a9fae4cc80c68d82cdf6e testing commit ae3419fbac845b4d3f3a9fae4cc80c68d82cdf6e gcc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 94b773f3df9149f49218179589e9902bedc48d255ed7d9933ec2d30398784d76 run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe run #1: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe run #2: crashed: possible deadlock in mnt_want_write_file run #3: crashed: possible deadlock in mnt_want_write_file run #4: crashed: possible deadlock in mnt_want_write_file run #5: crashed: possible deadlock in mnt_want_write_file run #6: crashed: possible deadlock in chown_common run #7: crashed: possible deadlock in mnt_want_write_file run #8: crashed: possible deadlock in mnt_want_write_file run #9: crashed: possible deadlock in chown_common revisions tested: 2, total time: 43m10.363034583s (build: 32m29.778232985s, test: 6m58.561262495s) the crash still happens on HEAD commit msg: vc_screen: don't clobber return value in vcs_read crash: possible deadlock in chown_common REISERFS (device loop0): checking transaction log (loop0) REISERFS (device loop0): Using rupasov hash to sort names REISERFS (device loop0): Created .reiserfs_priv - reserved for xattr storage. ====================================================== WARNING: possible circular locking dependency detected 6.2.0-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/5617 is trying to acquire lock: ffff8880735602e0 (&type->i_mutex_dir_key#8){+.+.}-{3:3}, at: chown_common+0x3b1/0x790 but task is already holding lock: ffff88807d6d0460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3a/0x70 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (sb_writers#13){.+.+}-{0:0}: lock_acquire+0x214/0x600 sb_start_write+0x47/0x130 mnt_want_write_file+0x5b/0x1a0 reiserfs_ioctl+0x149/0x2c0 __se_sys_ioctl+0xa7/0xf0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #1 (&sbi->lock){+.+.}-{3:3}: lock_acquire+0x214/0x600 __mutex_lock_common+0x1c2/0x2630 mutex_lock_nested+0x1b/0x20 reiserfs_write_lock+0x70/0xc0 reiserfs_lookup+0x121/0x3c0 __lookup_slow+0x217/0x300 lookup_one_len+0x1e0/0x230 reiserfs_lookup_privroot+0x85/0x1d0 reiserfs_fill_super+0x1bdf/0x20e0 mount_bdev+0x27f/0x370 legacy_get_tree+0xe9/0x170 vfs_get_tree+0x7f/0x220 do_new_mount+0x1e5/0x940 __se_sys_mount+0x20d/0x2a0 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&type->i_mutex_dir_key#8){+.+.}-{3:3}: validate_chain+0x166b/0x5860 __lock_acquire+0x125b/0x1f80 lock_acquire+0x214/0x600 down_write+0x3a/0x50 chown_common+0x3b1/0x790 do_fchownat+0x114/0x1c0 __x64_sys_lchown+0x80/0x90 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Chain exists of: &type->i_mutex_dir_key#8 --> &sbi->lock --> sb_writers#13 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(sb_writers#13); lock(&sbi->lock); lock(sb_writers#13); lock(&type->i_mutex_dir_key#8); *** DEADLOCK *** 1 lock held by syz-executor.0/5617: #0: ffff88807d6d0460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3a/0x70 stack backtrace: CPU: 1 PID: 5617 Comm: syz-executor.0 Not tainted 6.2.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023 Call Trace: dump_stack_lvl+0x12e/0x1d0 check_noncircular+0x2d1/0x390 validate_chain+0x166b/0x5860 __lock_acquire+0x125b/0x1f80 lock_acquire+0x214/0x600 down_write+0x3a/0x50 chown_common+0x3b1/0x790 do_fchownat+0x114/0x1c0 __x64_sys_lchown+0x80/0x90 do_syscall_64+0x41/0xc0 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f622488a5a9 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 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f6225a29168 EFLAGS: 00000246 ORIG_RAX: 000000000000005e RAX: ffffffffffffffda RBX: 00007f62249abf80 RCX: 00007f622488a5a9 RDX: 0000000000000000 RSI: 000000000000ee01 RDI: 0000000020000080 RBP: 00007f62248e5580 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffeb39e0c7f R14: 00007f6225a29300 R15: 0000000000022000