ci starts bisection 2023-03-04 09:00:37.491623588 +0000 UTC m=+254763.862876442 bisecting fixing commit since 6504d82f4440755d6fc1385532f84d0344243d61 building syzkaller on f371ed7e86e6a6b1b16a5700cd57055944574563 ensuring issue is reproducible on original commit 6504d82f4440755d6fc1385532f84d0344243d61 testing commit 6504d82f4440755d6fc1385532f84d0344243d61 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: 51a79456eccd56fc44c1ba1a85acc67513025571f8f0f8bd54cc61a5d70d3da0 run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe run #1: crashed: possible deadlock in ext4_xattr_get run #2: crashed: possible deadlock in ext4_xattr_get run #3: crashed: possible deadlock in ext4_xattr_get run #4: crashed: possible deadlock in ext4_xattr_get run #5: crashed: possible deadlock in ext4_xattr_get run #6: crashed: possible deadlock in ext4_xattr_get run #7: crashed: possible deadlock in ext4_xattr_get run #8: crashed: possible deadlock in ext4_xattr_get run #9: crashed: possible deadlock in ext4_xattr_get run #10: crashed: possible deadlock in ext4_xattr_get run #11: crashed: possible deadlock in ext4_xattr_get run #12: crashed: possible deadlock in ext4_xattr_get run #13: crashed: possible deadlock in ext4_xattr_get run #14: crashed: possible deadlock in ext4_xattr_get run #15: crashed: possible deadlock in ext4_xattr_get run #16: crashed: possible deadlock in ext4_xattr_get run #17: crashed: possible deadlock in ext4_xattr_get run #18: crashed: possible deadlock in ext4_xattr_get run #19: crashed: possible deadlock in ext4_xattr_get testing current HEAD 0988a0ea791999ebbf95693f2676381825b05033 testing commit 0988a0ea791999ebbf95693f2676381825b05033 gcc compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 kernel signature: cc720ba9ec343771a99df5fab5b24274741f5dca011c07c8c886a9d1a6b4e0c6 run #0: basic kernel testing failed: BUG: program execution failed: executor NUM: failed to write control pipe: write |NUM: broken pipe run #1: crashed: possible deadlock in ext4_xattr_get run #2: crashed: possible deadlock in ext4_xattr_get run #3: crashed: possible deadlock in ext4_xattr_get run #4: crashed: possible deadlock in ext4_xattr_get run #5: crashed: possible deadlock in ext4_xattr_get run #6: crashed: possible deadlock in ext4_xattr_get run #7: crashed: possible deadlock in ext4_xattr_get run #8: crashed: possible deadlock in ext4_xattr_get run #9: crashed: possible deadlock in ext4_xattr_get revisions tested: 2, total time: 21m30.474210949s (build: 13m48.393825253s, test: 6m35.51244793s) the crash still happens on HEAD commit msg: Merge tag 'for-v6.3-part2' of git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply crash: possible deadlock in ext4_xattr_get EXT4-fs (loop0): mounted filesystem 00000000-0000-0000-0000-000000000000 without journal. Quota mode: none. ====================================================== WARNING: possible circular locking dependency detected 6.2.0-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.0/5563 is trying to acquire lock: ffff8880746f75c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_get+0x11d/0x6f0 fs/ext4/xattr.c:726 but task is already holding lock: ffff8880746f7900 (&ea_inode->i_rwsem#7/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] ffff8880746f7900 (&ea_inode->i_rwsem#7/1){+.+.}-{3:3}, at: chown_common+0x2bf/0x5a0 fs/open.c:764 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ea_inode->i_rwsem#7/1){+.+.}-{3:3}: down_write+0x8e/0x200 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] ext4_xattr_inode_create fs/ext4/xattr.c:1525 [inline] ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1608 [inline] ext4_xattr_set_entry+0x2778/0x39d0 fs/ext4/xattr.c:1737 ext4_xattr_ibody_set+0xfa/0x330 fs/ext4/xattr.c:2289 ext4_xattr_set_handle+0x71c/0x10f0 fs/ext4/xattr.c:2446 ext4_xattr_set+0x123/0x2e0 fs/ext4/xattr.c:2560 __vfs_setxattr+0x109/0x160 fs/xattr.c:203 __vfs_setxattr_noperm+0xee/0x590 fs/xattr.c:237 vfs_setxattr+0x111/0x2d0 fs/xattr.c:324 setxattr+0x106/0x120 fs/xattr.c:632 path_setxattr+0x13c/0x170 fs/xattr.c:651 __do_sys_setxattr fs/xattr.c:667 [inline] __se_sys_setxattr fs/xattr.c:663 [inline] __x64_sys_setxattr+0xbb/0x150 fs/xattr.c:663 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 (&ei->xattr_sem){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x2ec7/0x5d40 kernel/locking/lockdep.c:5056 lock_acquire kernel/locking/lockdep.c:5669 [inline] lock_acquire+0x1df/0x670 kernel/locking/lockdep.c:5634 down_read+0x39/0x50 kernel/locking/rwsem.c:1520 ext4_xattr_get+0x11d/0x6f0 fs/ext4/xattr.c:726 __vfs_getxattr+0xe6/0x140 fs/xattr.c:426 cap_inode_need_killpriv+0x37/0x50 security/commoncap.c:301 security_inode_need_killpriv+0x34/0x70 security/security.c:1492 notify_change+0x410/0xda0 fs/attr.c:415 chown_common+0x4a0/0x5a0 fs/open.c:774 do_fchownat+0xcf/0x140 fs/open.c:805 __do_sys_fchownat fs/open.c:820 [inline] __se_sys_fchownat fs/open.c:817 [inline] __x64_sys_fchownat+0xb5/0x150 fs/open.c:817 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 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ea_inode->i_rwsem#7/1); lock(&ei->xattr_sem); lock(&ea_inode->i_rwsem#7/1); lock(&ei->xattr_sem); *** DEADLOCK *** 2 locks held by syz-executor.0/5563: #0: ffff888028c0c460 (sb_writers#5){.+.+}-{0:0}, at: do_fchownat+0xb8/0x140 fs/open.c:802 #1: ffff8880746f7900 (&ea_inode->i_rwsem#7/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #1: ffff8880746f7900 (&ea_inode->i_rwsem#7/1){+.+.}-{3:3}, at: chown_common+0x2bf/0x5a0 fs/open.c:764 stack backtrace: CPU: 1 PID: 5563 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 lib/dump_stack.c:88 [inline] dump_stack_lvl+0x60/0xa0 lib/dump_stack.c:106 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3098 [inline] check_prevs_add kernel/locking/lockdep.c:3217 [inline] validate_chain kernel/locking/lockdep.c:3832 [inline] __lock_acquire+0x2ec7/0x5d40 kernel/locking/lockdep.c:5056 lock_acquire kernel/locking/lockdep.c:5669 [inline] lock_acquire+0x1df/0x670 kernel/locking/lockdep.c:5634 down_read+0x39/0x50 kernel/locking/rwsem.c:1520 ext4_xattr_get+0x11d/0x6f0 fs/ext4/xattr.c:726 __vfs_getxattr+0xe6/0x140 fs/xattr.c:426 cap_inode_need_killpriv+0x37/0x50 security/commoncap.c:301 security_inode_need_killpriv+0x34/0x70 security/security.c:1492 notify_change+0x410/0xda0 fs/attr.c:415 chown_common+0x4a0/0x5a0 fs/open.c:774 do_fchownat+0xcf/0x140 fs/open.c:805 __do_sys_fchownat fs/open.c:820 [inline] __se_sys_fchownat fs/open.c:817 [inline] __x64_sys_fchownat+0xb5/0x150 fs/open.c:817 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 RIP: 0033:0x7f8bb98893c9 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:00007f8bba9a9168 EFLAGS: 00000246 ORIG_RAX: 0000000000000104 RAX: ffffffffffffffda RBX: 00007f8bb999bf80 RCX: 00007f8bb98893c9 RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000000000005 RBP: 00007f8bb98e433f R08: 0000000000001000 R09: 0000000000000000 R10: 000000000000ee01 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ffca3a543bf R14: 00007f8bba9a9300 R15: 0000000000022000