syzbot


INFO: task hung in ext4_evict_ea_inode (3)

Status: upstream: reported syz repro on 2025/02/05 21:10
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+dcbb6d5fad7fa4c81139@syzkaller.appspotmail.com
First crash: 194d, last: 19d
Cause bisection: failed (error log, bisect log)
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ext4?] INFO: task hung in ext4_evict_ea_inode (3) 0 (1) 2025/02/05 21:10
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in ext4_evict_ea_inode (2) ext4 1 294d 294d 0/28 auto-obsoleted due to no activity on 2024/09/05 05:22
linux-6.1 INFO: task hung in ext4_evict_ea_inode 1 646d 646d 0/3 auto-obsoleted due to no activity on 2023/09/29 02:02
linux-6.1 INFO: task hung in ext4_evict_ea_inode (2) origin:lts-only syz error 4 78d 126d 0/3 upstream: reported syz repro on 2024/11/21 22:54
upstream INFO: task hung in ext4_evict_ea_inode ext4 syz done unreliable 6 578d 807d 0/28 auto-obsoleted due to no activity on 2023/12/06 15:41
Last patch testing requests (2)
Created Duration User Patch Repo Result
2025/03/23 06:36 21m retest repro upstream OK log
2025/02/15 21:11 24m retest repro upstream OK log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2025/03/03 20:58 5h51m (2) bisect fix upstream OK (0) job log log

Sample crash report:
INFO: task syz.1.197:6818 blocked for more than 144 seconds.
      Not tainted 6.14.0-rc5-syzkaller-00218-g2a520073e74f #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.197       state:D stack:22912 pid:6818  tgid:6817  ppid:5835   task_flags:0x400140 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5378 [inline]
 __schedule+0x190e/0x4c90 kernel/sched/core.c:6765
 __schedule_loop kernel/sched/core.c:6842 [inline]
 schedule+0x14b/0x320 kernel/sched/core.c:6857
 mb_cache_entry_wait_unused+0x166/0x250 fs/mbcache.c:148
 ext4_evict_ea_inode+0x14a/0x2f0 fs/ext4/xattr.c:480
 ext4_evict_inode+0x194/0xf50 fs/ext4/inode.c:185
 evict+0x4ea/0x9a0 fs/inode.c:796
 ext4_xattr_inode_array_free+0x7b/0x100 fs/ext4/xattr.c:3029
 ext4_evict_inode+0xc63/0xf50 fs/ext4/inode.c:312
 evict+0x4ea/0x9a0 fs/inode.c:796
 __dentry_kill+0x20d/0x630 fs/dcache.c:643
 dput+0x19f/0x2b0 fs/dcache.c:885
 do_renameat2+0xda1/0x13f0 fs/namei.c:5228
 __do_sys_rename fs/namei.c:5273 [inline]
 __se_sys_rename fs/namei.c:5271 [inline]
 __x64_sys_rename+0x82/0x90 fs/namei.c:5271
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc55418d169
RSP: 002b:00007fc553ff9038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fc5543a5fa0 RCX: 00007fc55418d169
RDX: 0000000000000000 RSI: 00004000000000c0 RDI: 0000400000000000
RBP: 00007fc55420e2a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fc5543a5fa0 R15: 00007ffd82c01ab8
 </TASK>
INFO: task syz.1.197:6843 blocked for more than 146 seconds.
      Not tainted 6.14.0-rc5-syzkaller-00218-g2a520073e74f #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.197       state:D stack:25360 pid:6843  tgid:6817  ppid:5835   task_flags:0x400140 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5378 [inline]
 __schedule+0x190e/0x4c90 kernel/sched/core.c:6765
 __schedule_loop kernel/sched/core.c:6842 [inline]
 schedule+0x14b/0x320 kernel/sched/core.c:6857
 __wait_on_freeing_inode+0x1c7/0x2f0 fs/inode.c:2502
 find_inode_fast+0x2ab/0x480 fs/inode.c:1103
 iget_locked+0x96/0x5a0 fs/inode.c:1475
 __ext4_iget+0x25e/0x3f30 fs/ext4/inode.c:4760
 ext4_xattr_inode_cache_find fs/ext4/xattr.c:1548 [inline]
 ext4_xattr_inode_lookup_create+0x3c0/0x1c70 fs/ext4/xattr.c:1587
 ext4_xattr_ibody_set+0x214/0x730 fs/ext4/xattr.c:2269
 ext4_xattr_set_handle+0xba6/0x1580 fs/ext4/xattr.c:2446
 ext4_xattr_set+0x280/0x3e0 fs/ext4/xattr.c:2560
 __vfs_setxattr+0x46a/0x4a0 fs/xattr.c:200
 __vfs_setxattr_noperm+0x12e/0x660 fs/xattr.c:234
 vfs_setxattr+0x221/0x430 fs/xattr.c:321
 do_setxattr fs/xattr.c:636 [inline]
 filename_setxattr+0x2af/0x430 fs/xattr.c:665
 path_setxattrat+0x440/0x510 fs/xattr.c:713
 __do_sys_setxattr fs/xattr.c:747 [inline]
 __se_sys_setxattr fs/xattr.c:743 [inline]
 __x64_sys_setxattr+0xbc/0xe0 fs/xattr.c:743
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fc55418d169
RSP: 002b:00007fc553fb7038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007fc5543a6160 RCX: 00007fc55418d169
RDX: 0000400000001400 RSI: 00004000000001c0 RDI: 0000400000000380
RBP: 00007fc55420e2a0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000835 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fc5543a6160 R15: 00007ffd82c01ab8
 </TASK>

Showing all locks held in the system:
3 locks held by kworker/u8:0/12:
 #0: ffff8880b873e958 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:598
 #1: ffff8880b8728948 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x41d/0x7a0 kernel/sched/psi.c:987
 #2: ffff8880b872a398 (&base->lock){-.-.}-{2:2}, at: lock_timer_base kernel/time/timer.c:1046 [inline]
 #2: ffff8880b872a398 (&base->lock){-.-.}-{2:2}, at: __mod_timer+0x24a/0x10e0 kernel/time/timer.c:1127
1 lock held by khungtaskd/31:
 #0: ffffffff8eb39320 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:337 [inline]
 #0: ffffffff8eb39320 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:849 [inline]
 #0: ffffffff8eb39320 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6746
1 lock held by klogd/5192:
 #0: ffff8880b873e958 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:598
2 locks held by getty/5587:
 #0: ffff88803571a0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002fde2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x616/0x1770 drivers/tty/n_tty.c:2211
3 locks held by kworker/0:4/5891:
 #0: ffff88801b078d48 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3213 [inline]
 #0: ffff88801b078d48 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x98b/0x18e0 kernel/workqueue.c:3319
 #1: ffffc90004c7fc60 (key_gc_work){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3214 [inline]
 #1: ffffc90004c7fc60 (key_gc_work){+.+.}-{0:0}, at: process_scheduled_works+0x9c6/0x18e0 kernel/workqueue.c:3319
 #2: ffffffff8eb3e7f8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:302 [inline]
 #2: ffffffff8eb3e7f8 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x381/0x820 kernel/rcu/tree_exp.h:996
4 locks held by syz.1.197/6818:
 #0: ffff88805daec420 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:547
 #1: ffff88805daec730 (&type->s_vfs_rename_key#2){+.+.}-{4:4}, at: lock_rename fs/namei.c:3221 [inline]
 #1: ffff88805daec730 (&type->s_vfs_rename_key#2){+.+.}-{4:4}, at: do_renameat2+0x5cf/0x13f0 fs/namei.c:5161
 #2: ffff888076b3c950 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:912 [inline]
 #2: ffff888076b3c950 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: lock_two_directories+0x145/0x220 fs/namei.c:3187
 #3: ffff88823bfd83f8 (&type->i_mutex_dir_key#3/5){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:912 [inline]
 #3: ffff88823bfd83f8 (&type->i_mutex_dir_key#3/5){+.+.}-{4:4}, at: lock_two_directories+0x16f/0x220 fs/namei.c:3188
3 locks held by syz.1.197/6843:
 #0: ffff88805daec420 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:547
 #1: ffff888076b3f0f0 (&sb->s_type->i_mutex_key#8){++++}-{4:4}, at: inode_lock include/linux/fs.h:877 [inline]
 #1: ffff888076b3f0f0 (&sb->s_type->i_mutex_key#8){++++}-{4:4}, at: vfs_setxattr+0x1e1/0x430 fs/xattr.c:320
 #2: ffff888076b3edc0 (&ei->xattr_sem){++++}-{4:4}, at: ext4_write_lock_xattr fs/ext4/xattr.h:154 [inline]
 #2: ffff888076b3edc0 (&ei->xattr_sem){++++}-{4:4}, at: ext4_xattr_set_handle+0x277/0x1580 fs/ext4/xattr.c:2373

=============================================

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.14.0-rc5-syzkaller-00218-g2a520073e74f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x49c/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x198/0x320 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:162 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:236 [inline]
 watchdog+0x1058/0x10a0 kernel/hung_task.c:399
 kthread+0x7ab/0x920 kernel/kthread.c:464
 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:48 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:106 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt+0x21/0x30 drivers/acpi/processor_idle.c:111

Crashes (12):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/09 06:32 upstream 2a520073e74f 163f510d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in ext4_evict_ea_inode
2025/02/01 20:56 upstream 69e858e0b8b2 0dff8567 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in ext4_evict_ea_inode
2025/02/01 13:24 upstream 69e858e0b8b2 0dff8567 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in ext4_evict_ea_inode
2024/12/25 16:57 upstream 9b2ffa6148b1 444551c4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in ext4_evict_ea_inode
2024/12/07 06:39 upstream b5f217084ab3 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in ext4_evict_ea_inode
2024/12/01 22:13 upstream bcc8eda6d349 68914665 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in ext4_evict_ea_inode
2024/09/20 10:17 upstream 2004cef11ea0 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in ext4_evict_ea_inode
2024/09/15 01:57 upstream 0babf683783d 08d8a733 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in ext4_evict_ea_inode
2024/09/14 21:54 upstream 0babf683783d ff60e2ca .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in ext4_evict_ea_inode
2025/03/05 14:45 upstream 48a5eed9ad58 60f5d8d9 .config console log report syz / log [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (clean fs)] ci-snapshot-upstream-root INFO: task hung in ext4_evict_ea_inode
2024/12/18 17:09 linux-next 7fa366f1b6e3 1432fc84 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in ext4_evict_ea_inode
2024/11/27 05:27 linux-next 6f3d2b5299b0 52b38cc1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in ext4_evict_ea_inode
* Struck through repros no longer work on HEAD.