syzbot |
sign-in | mailing list | source | docs |
🐞 Open [1163] 🐞 Fixed [4320] 🐞 Invalid [9666] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes |
Kernel | Title | Repro | Cause bisect | Fix bisect | Count | Last | Reported | Patched | Status |
---|---|---|---|---|---|---|---|---|---|
linux-4.14 | possible deadlock in ext4_xattr_get | C | inconclusive | 1 | 284d | 284d | 0/1 | upstream: reported C repro on 2022/04/27 03:33 | |
linux-4.19 | possible deadlock in ext4_xattr_get | C | error | 1 | 284d | 284d | 0/1 | upstream: reported C repro on 2022/04/27 05:09 |
Created | Duration | User | Patch | Repo | Result |
---|---|---|---|---|---|
2022/12/22 07:31 | 12m | retest repro | upstream | report log | |
2022/08/08 13:32 | 15m | hdanton@sina.com | patch | https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cb71b93c2dc3 | OK log |
2022/08/08 12:10 | 9m | hdanton@sina.com | patch | https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cb71b93c2dc3 | report log |
2022/08/08 11:14 | 10m | hdanton@sina.com | patch | https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cb71b93c2dc3 | report log |
====================================================== WARNING: possible circular locking dependency detected 6.0.0-rc5-syzkaller-00007-g6504d82f4440 #0 Not tainted ------------------------------------------------------ syz-executor384/3606 is trying to acquire lock: ffff88806d467208 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_get+0x14e/0x740 fs/ext4/xattr.c:665 but task is already holding lock: ffff88806d467540 (&ea_inode->i_rwsem#7/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline] ffff88806d467540 (&ea_inode->i_rwsem#7/1){+.+.}-{3:3}, at: chown_common+0x364/0x710 fs/open.c:727 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+0x90/0x150 kernel/locking/rwsem.c:1552 inode_lock include/linux/fs.h:756 [inline] ext4_xattr_inode_create fs/ext4/xattr.c:1454 [inline] ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1537 [inline] ext4_xattr_set_entry+0x2b38/0x3980 fs/ext4/xattr.c:1665 ext4_xattr_ibody_set+0x12d/0x3a0 fs/ext4/xattr.c:2225 ext4_xattr_set_handle+0x964/0x1500 fs/ext4/xattr.c:2382 ext4_xattr_set+0x13a/0x340 fs/ext4/xattr.c:2495 __vfs_setxattr+0x115/0x180 fs/xattr.c:182 __vfs_setxattr_noperm+0x125/0x5f0 fs/xattr.c:216 __vfs_setxattr_locked+0x1cf/0x260 fs/xattr.c:277 vfs_setxattr+0x11e/0x3c0 fs/xattr.c:313 setxattr+0x146/0x160 fs/xattr.c:623 path_setxattr+0x197/0x1c0 fs/xattr.c:642 __do_sys_setxattr fs/xattr.c:658 [inline] __se_sys_setxattr fs/xattr.c:654 [inline] __x64_sys_setxattr+0xc0/0x160 fs/xattr.c:654 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:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3829 [inline] __lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5053 lock_acquire kernel/locking/lockdep.c:5666 [inline] lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5631 down_read+0x98/0x450 kernel/locking/rwsem.c:1499 ext4_xattr_get+0x14e/0x740 fs/ext4/xattr.c:665 __vfs_getxattr+0xd9/0x140 fs/xattr.c:411 cap_inode_need_killpriv+0x3c/0x60 security/commoncap.c:301 security_inode_need_killpriv+0x40/0x90 security/security.c:1420 notify_change+0x6e7/0x1440 fs/attr.c:353 chown_common+0x61b/0x710 fs/open.c:734 do_fchownat+0x126/0x1e0 fs/open.c:765 __do_sys_fchownat fs/open.c:780 [inline] __se_sys_fchownat fs/open.c:777 [inline] __x64_sys_fchownat+0xba/0x150 fs/open.c:777 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-executor384/3606: #0: ffff888028a20460 (sb_writers#5){.+.+}-{0:0}, at: do_fchownat+0x101/0x1e0 fs/open.c:762 #1: ffff88806d467540 (&ea_inode->i_rwsem#7/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline] #1: ffff88806d467540 (&ea_inode->i_rwsem#7/1){+.+.}-{3:3}, at: chown_common+0x364/0x710 fs/open.c:727 stack backtrace: CPU: 1 PID: 3606 Comm: syz-executor384 Not tainted 6.0.0-rc5-syzkaller-00007-g6504d82f4440 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 check_noncircular+0x25f/0x2e0 kernel/locking/lockdep.c:2175 check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3829 [inline] __lock_acquire+0x2a43/0x56d0 kernel/locking/lockdep.c:5053 lock_acquire kernel/locking/lockdep.c:5666 [inline] lock_acquire+0x1ab/0x570 kernel/locking/lockdep.c:5631 down_read+0x98/0x450 kernel/locking/rwsem.c:1499 ext4_xattr_get+0x14e/0x740 fs/ext4/xattr.c:665 __vfs_getxattr+0xd9/0x140 fs/xattr.c:411 cap_inode_need_killpriv+0x3c/0x60 security/commoncap.c:301 security_inode_need_killpriv+0x40/0x90 security/security.c:1420 notify_change+0x6e7/0x1440 fs/attr.c:353 chown_common+0x61b/0x710 fs/open.c:734 do_fchownat+0x126/0x1e0 fs/open.c:765 __do_sys_fchownat fs/open.c:780 [inline] __se_sys_fchownat fs/open.c:777 [inline] __x64_sys_fchownat+0xba/0x150 fs/open.c:777 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:0x7f2c842f20e9 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 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffd30187fd8 EFLAGS: 00000246 ORIG_RAX: 0000000000000104 RAX: ffffffffffffffda RBX: 2f30656c69662f2e RCX: 00007f2c842f20e9 RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000000000005
Manager | Time | Kernel | Commit | Syzkaller | Config | Log | Report | Syz repro | C repro | VM info | Assets | Title |
---|---|---|---|---|---|---|---|---|---|---|---|---|
ci-upstream-kasan-gce-selinux-root | 2023/02/02 07:47 | upstream | 9f266ccaa2f5 | f371ed7e | .config | console log | report | syz | C | |||
ci-upstream-kasan-gce-selinux-root | 2022/12/31 12:25 | upstream | 6504d82f4440 | f371ed7e | .config | console log | report | syz | C |
Manager | Time | Kernel | Commit | Syzkaller | Config | Log | Report | Syz repro | C repro | VM info | Assets | Title |
---|---|---|---|---|---|---|---|---|---|---|---|---|
ci-upstream-kasan-gce-selinux-root | 2022/09/13 06:51 | upstream | 6504d82f4440 | f371ed7e | .config | strace log | report | syz | C | [disk image] [vmlinux] | possible deadlock in ext4_xattr_get | |
ci-upstream-kasan-gce-smack-root | 2022/08/14 18:48 | upstream | 7ebfc85e2cd7 | 8dfcaa3d | .config | strace log | report | syz | C | possible deadlock in ext4_xattr_get | ||
ci-upstream-linux-next-kasan-gce-root | 2022/08/03 13:00 | linux-next | cb71b93c2dc3 | 1c9013ac | .config | strace log | report | syz | C | possible deadlock in ext4_xattr_get |