syzbot


possible deadlock in vfs_removexattr

Status: auto-obsoleted due to no activity on 2024/07/12 03:33
Reported-by: syzbot+dec0bdd3641f08d2b338@syzkaller.appspotmail.com
First crash: 232d, last: 232d
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream possible deadlock in vfs_removexattr (2) reiserfs 2 303d 304d 0/28 auto-obsoleted due to no activity on 2024/05/01 20:00
linux-6.1 possible deadlock in vfs_removexattr 2 192d 192d 0/3 auto-obsoleted due to no activity on 2024/08/21 05:03
upstream possible deadlock in vfs_removexattr reiserfs 1 525d 520d 0/28 auto-obsoleted due to no activity on 2023/09/22 21:50

Sample crash report:
======================================================
WARNING: possible circular locking dependency detected
5.15.153-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor.0/6276 is trying to acquire lock:
ffff0000eb410980 (&type->i_mutex_dir_key#8){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline]
ffff0000eb410980 (&type->i_mutex_dir_key#8){+.+.}-{3:3}, at: vfs_removexattr+0xcc/0x23c fs/xattr.c:526

but task is already holding lock:
ffff0000c8c2e460 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (sb_writers#14){.+.+}-{0:0}:
       percpu_down_read include/linux/percpu-rwsem.h:51 [inline]
       __sb_start_write include/linux/fs.h:1787 [inline]
       sb_start_write+0xf0/0x3ac include/linux/fs.h:1857
       mnt_want_write_file+0x64/0x1e8 fs/namespace.c:421
       reiserfs_ioctl+0x188/0x4b8 fs/reiserfs/ioctl.c:103
       vfs_ioctl fs/ioctl.c:51 [inline]
       __do_sys_ioctl fs/ioctl.c:874 [inline]
       __se_sys_ioctl fs/ioctl.c:860 [inline]
       __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
       do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
       el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
       el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

-> #1 (&sbi->lock){+.+.}-{3:3}:
       __mutex_lock_common+0x194/0x2154 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
       reiserfs_write_lock+0x7c/0xe8 fs/reiserfs/lock.c:27
       reiserfs_lookup+0x130/0x3c4 fs/reiserfs/namei.c:364
       __lookup_slow+0x250/0x388 fs/namei.c:1663
       lookup_one_len+0x178/0x28c fs/namei.c:2718
       reiserfs_lookup_privroot+0x8c/0x204 fs/reiserfs/xattr.c:980
       reiserfs_fill_super+0x1aec/0x1e8c fs/reiserfs/super.c:2178
       mount_bdev+0x274/0x370 fs/super.c:1387
       get_super_block+0x44/0x58 fs/reiserfs/super.c:2608
       legacy_get_tree+0xd4/0x16c fs/fs_context.c:611
       vfs_get_tree+0x90/0x274 fs/super.c:1517
       do_new_mount+0x278/0x8fc fs/namespace.c:3005
       path_mount+0x594/0x101c fs/namespace.c:3335
       do_mount fs/namespace.c:3348 [inline]
       __do_sys_mount fs/namespace.c:3556 [inline]
       __se_sys_mount fs/namespace.c:3533 [inline]
       __arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3533
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
       do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
       el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
       el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

-> #0 (&type->i_mutex_dir_key#8){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x32d4/0x7638 kernel/locking/lockdep.c:5012
       lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5623
       down_write+0x110/0x260 kernel/locking/rwsem.c:1541
       inode_lock include/linux/fs.h:789 [inline]
       vfs_removexattr+0xcc/0x23c fs/xattr.c:526
       removexattr fs/xattr.c:857 [inline]
       path_removexattr+0x1ec/0x2ec fs/xattr.c:871
       __do_sys_removexattr fs/xattr.c:885 [inline]
       __se_sys_removexattr fs/xattr.c:882 [inline]
       __arm64_sys_removexattr+0x60/0x78 fs/xattr.c:882
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
       do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
       el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
       el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
       el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

other info that might help us debug this:

Chain exists of:
  &type->i_mutex_dir_key#8 --> &sbi->lock --> sb_writers#14

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(sb_writers#14);
                               lock(&sbi->lock);
                               lock(sb_writers#14);
  lock(&type->i_mutex_dir_key#8);

 *** DEADLOCK ***

1 lock held by syz-executor.0/6276:
 #0: ffff0000c8c2e460 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377

stack backtrace:
CPU: 1 PID: 6276 Comm: syz-executor.0 Not tainted 5.15.153-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call trace:
 dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 dump_stack+0x1c/0x58 lib/dump_stack.c:113
 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2011
 check_noncircular+0x2cc/0x378 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x32d4/0x7638 kernel/locking/lockdep.c:5012
 lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5623
 down_write+0x110/0x260 kernel/locking/rwsem.c:1541
 inode_lock include/linux/fs.h:789 [inline]
 vfs_removexattr+0xcc/0x23c fs/xattr.c:526
 removexattr fs/xattr.c:857 [inline]
 path_removexattr+0x1ec/0x2ec fs/xattr.c:871
 __do_sys_removexattr fs/xattr.c:885 [inline]
 __se_sys_removexattr fs/xattr.c:882 [inline]
 __arm64_sys_removexattr+0x60/0x78 fs/xattr.c:882
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/04/03 03:32 linux-5.15.y 9465fef4ae35 7925100d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 possible deadlock in vfs_removexattr
* Struck through repros no longer work on HEAD.