[v5.15] INFO: task hung in ext4_evict_ea_inode
0 views
Skip to first unread message
syzbot
Oct 7, 2025, 12:26:27 AM (yesterday) Oct 7
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 29e53a5b1c4f Linux 5.15.194
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=144041e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=482d466cac2da73e8da6
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8cd4e3ff852c/disk-29e53a5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/21e1f773622c/vmlinux-29e53a5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8f418c0a25cc/bzImage-29e53a5b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+482d46...@syzkaller.appspotmail.com
INFO: task syz.9.888:8342 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.9.888 state:D stack:24704 pid: 8342 ppid: 7421 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
mb_cache_entry_wait_unused+0x164/0x240 fs/mbcache.c:148
ext4_evict_ea_inode+0x149/0x2f0 fs/ext4/xattr.c:444
ext4_evict_inode+0x156/0x1080 fs/ext4/inode.c:183
evict+0x485/0x870 fs/inode.c:647
ext4_xattr_set_entry+0x10f7/0x3d30 fs/ext4/xattr.c:1835
ext4_xattr_block_set+0x4f7/0x2d30 fs/ext4/xattr.c:1935
ext4_xattr_set_handle+0xbd5/0x12b0 fs/ext4/xattr.c:2421
ext4_xattr_set+0x22a/0x320 fs/ext4/xattr.c:2522
__vfs_setxattr+0x3e0/0x420 fs/xattr.c:182
__vfs_setxattr_noperm+0x129/0x5e0 fs/xattr.c:216
vfs_setxattr+0x168/0x2f0 fs/xattr.c:303
do_setxattr fs/xattr.c:588 [inline]
setxattr+0x2da/0x300 fs/xattr.c:611
path_setxattr+0x142/0x280 fs/xattr.c:630
__do_sys_setxattr fs/xattr.c:646 [inline]
__se_sys_setxattr fs/xattr.c:642 [inline]
__x64_sys_setxattr+0xb7/0xd0 fs/xattr.c:642
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fcaa4351ec9
RSP: 002b:00007fcaa25b9038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007fcaa45a8fa0 RCX: 00007fcaa4351ec9
RDX: 0000200000001400 RSI: 0000200000000080 RDI: 00002000000000c0
RBP: 00007fcaa43d4f91 R08: 0000000000000002 R09: 0000000000000000
R10: 0000000000000835 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fcaa45a9038 R14: 00007fcaa45a8fa0 R15: 00007ffef705e8d8
</TASK>
INFO: task syz.9.888:8350 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.9.888 state:D stack:26408 pid: 8350 ppid: 7421 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
__wait_on_freeing_inode fs/inode.c:2139 [inline]
find_inode_fast+0x2b9/0x3c0 fs/inode.c:933
iget_locked+0xb4/0x820 fs/inode.c:1295
__ext4_iget+0x230/0x3d90 fs/ext4/inode.c:4669
ext4_xattr_inode_cache_find fs/ext4/xattr.c:1508 [inline]
ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1543 [inline]
ext4_xattr_set_entry+0x1f90/0x3d30 fs/ext4/xattr.c:1684
ext4_xattr_block_set+0x973/0x2d30 fs/ext4/xattr.c:2004
ext4_xattr_set_handle+0xbd5/0x12b0 fs/ext4/xattr.c:2421
ext4_xattr_set+0x22a/0x320 fs/ext4/xattr.c:2522
__vfs_setxattr+0x3e0/0x420 fs/xattr.c:182
__vfs_setxattr_noperm+0x129/0x5e0 fs/xattr.c:216
vfs_setxattr+0x168/0x2f0 fs/xattr.c:303
do_setxattr fs/xattr.c:588 [inline]
setxattr+0x2da/0x300 fs/xattr.c:611
path_setxattr+0x142/0x280 fs/xattr.c:630
__do_sys_setxattr fs/xattr.c:646 [inline]
__se_sys_setxattr fs/xattr.c:642 [inline]
__x64_sys_setxattr+0xb7/0xd0 fs/xattr.c:642
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fcaa4351ec9
RSP: 002b:00007fcaa2598038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007fcaa45a9090 RCX: 00007fcaa4351ec9
RDX: 0000200000001400 RSI: 00002000000001c0 RDI: 0000200000000380
RBP: 00007fcaa43d4f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000835 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fcaa45a9128 R14: 00007fcaa45a9090 R15: 00007ffef705e8d8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/u4:2/154:
#0: ffff8881433f2938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90002057d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff888016a820e0 (&type->s_umount_key#41){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
2 locks held by getty/3946:
#0: ffff88802bff1098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900025e62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
3 locks held by kworker/1:13/4534:
#0: ffff888016870938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90003edfd00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff88807c0f8240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x271/0x3240 drivers/net/netdevsim/fib.c:1480
2 locks held by kworker/0:16/6215:
#0: ffff888016872138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90003f7fd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
3 locks held by syz.9.888/8342:
#0: ffff88805f69a460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
#1: ffff88805f3917e0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805f3917e0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: vfs_setxattr+0x141/0x2f0 fs/xattr.c:302
#2: ffff88805f3914b8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline]
#2: ffff88805f3914b8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_set_handle+0x171/0x12b0 fs/ext4/xattr.c:2336
3 locks held by syz.9.888/8350:
#0: ffff88805f69a460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
#1: ffff88805f3903f0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805f3903f0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: vfs_setxattr+0x141/0x2f0 fs/xattr.c:302
#2: ffff88805f3900c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline]
#2: ffff88805f3900c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_set_handle+0x171/0x12b0 fs/ext4/xattr.c:2336
1 lock held by syz.5.1148/9442:
#0: ffff88801ffabd18 (&disk->open_mutex){+.+.}-{3:3}, at: sync_bdevs+0x1ab/0x320 block/bdev.c:1053
2 locks held by syz.4.1311/10243:
#0: ffff888061c5ec70 (&fc->uapi_mutex){+.+.}-{3:3}, at: __do_sys_fsconfig fs/fsopen.c:437 [inline]
#0: ffff888061c5ec70 (&fc->uapi_mutex){+.+.}-{3:3}, at: __se_sys_fsconfig+0x5ec/0x750 fs/fsopen.c:314
#1: ffff88801ffabd18 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x157/0xa60 block/bdev.c:820
3 locks held by syz-executor/10773:
#0: ffff888057200ff0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x5f/0x1030 net/bluetooth/hci_core.c:1737
#1: ffff888057200078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_do_close+0x3f4/0x1030 net/bluetooth/hci_core.c:1782
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1517 [inline]
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xa4/0x220 net/bluetooth/hci_conn.c:1622
4 locks held by syz-executor/11756:
3 locks held by syz.0.1621/12083:
#0: ffff888059644ff0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x5f/0x1030 net/bluetooth/hci_core.c:1737
#1: ffff888059644078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_do_close+0x3f4/0x1030 net/bluetooth/hci_core.c:1782
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1517 [inline]
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xa4/0x220 net/bluetooth/hci_conn.c:1622
1 lock held by syz-executor/12461:
#0: ffff88801ffabd18 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x157/0xa60 block/bdev.c:820
1 lock held by rm/12661:
#0: ffff888065e47128 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff888065e47128 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:549
4 locks held by syz-executor/12675:
#0: ffff88807691cff0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x5f/0x1030 net/bluetooth/hci_core.c:1737
#1: ffff88807691c078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_do_close+0x3f4/0x1030 net/bluetooth/hci_core.c:1782
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1517 [inline]
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xa4/0x220 net/bluetooth/hci_conn.c:1622
#3: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#3: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x347/0x6b0 kernel/rcu/tree_exp.h:845
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5034 Comm: kworker/u4:14 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:arch_irqs_disabled_flags arch/x86/include/asm/irqflags.h:127 [inline]
RIP: 0010:check_preemption_disabled+0x59/0x110 lib/smp_processor_id.c:19
Code: 48 8b 0c 25 28 00 00 00 48 3b 4c 24 08 0f 85 c4 00 00 00 48 83 c4 10 5b 41 5e 41 5f 5d c3 48 c7 04 24 00 00 00 00 9c 8f 04 24 <f7> 04 24 00 02 00 00 74 cc 65 4c 8b 3d b6 30 59 76 41 f6 47 2f 04
RSP: 0018:ffffc9000346fa88 EFLAGS: 00000046
RAX: 0000000000000001 RBX: ffff88802abf8000 RCX: 0000000080000000
RDX: 0000000000000000 RSI: ffffffff8a0b2620 RDI: ffffffff8a59a4c0
RBP: ffffc9000346fbd0 R08: dffffc0000000000 R09: fffffbfff1ad32b6
R10: fffffbfff1ad32b6 R11: 1ffffffff1ad32b5 R12: 000000000000037c
R13: dffffc0000000000 R14: ffff88802abf8aec R15: 1ffff9200068df64
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3014901e80 CR3: 000000002a703000 CR4: 00000000003506e0
DR0: 0000000000000004 DR1: 0000000000000006 DR2: 0000000000000005
DR3: fffffffffffffff1 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lockdep_recursion_inc kernel/locking/lockdep.c:431 [inline]
lock_release+0x156/0x870 kernel/locking/lockdep.c:5642
rcu_read_unlock include/linux/rcupdate.h:772 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:416 [inline]
batadv_nc_worker+0x25b/0x5c0 net/batman-adv/network-coding.c:723
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
syzbot found the following issue on:
HEAD commit: 29e53a5b1c4f Linux 5.15.194
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=144041e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=482d466cac2da73e8da6
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8cd4e3ff852c/disk-29e53a5b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/21e1f773622c/vmlinux-29e53a5b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8f418c0a25cc/bzImage-29e53a5b.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+482d46...@syzkaller.appspotmail.com
INFO: task syz.9.888:8342 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.9.888 state:D stack:24704 pid: 8342 ppid: 7421 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
mb_cache_entry_wait_unused+0x164/0x240 fs/mbcache.c:148
ext4_evict_ea_inode+0x149/0x2f0 fs/ext4/xattr.c:444
ext4_evict_inode+0x156/0x1080 fs/ext4/inode.c:183
evict+0x485/0x870 fs/inode.c:647
ext4_xattr_set_entry+0x10f7/0x3d30 fs/ext4/xattr.c:1835
ext4_xattr_block_set+0x4f7/0x2d30 fs/ext4/xattr.c:1935
ext4_xattr_set_handle+0xbd5/0x12b0 fs/ext4/xattr.c:2421
ext4_xattr_set+0x22a/0x320 fs/ext4/xattr.c:2522
__vfs_setxattr+0x3e0/0x420 fs/xattr.c:182
__vfs_setxattr_noperm+0x129/0x5e0 fs/xattr.c:216
vfs_setxattr+0x168/0x2f0 fs/xattr.c:303
do_setxattr fs/xattr.c:588 [inline]
setxattr+0x2da/0x300 fs/xattr.c:611
path_setxattr+0x142/0x280 fs/xattr.c:630
__do_sys_setxattr fs/xattr.c:646 [inline]
__se_sys_setxattr fs/xattr.c:642 [inline]
__x64_sys_setxattr+0xb7/0xd0 fs/xattr.c:642
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fcaa4351ec9
RSP: 002b:00007fcaa25b9038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007fcaa45a8fa0 RCX: 00007fcaa4351ec9
RDX: 0000200000001400 RSI: 0000200000000080 RDI: 00002000000000c0
RBP: 00007fcaa43d4f91 R08: 0000000000000002 R09: 0000000000000000
R10: 0000000000000835 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fcaa45a9038 R14: 00007fcaa45a8fa0 R15: 00007ffef705e8d8
</TASK>
INFO: task syz.9.888:8350 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.9.888 state:D stack:26408 pid: 8350 ppid: 7421 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
__wait_on_freeing_inode fs/inode.c:2139 [inline]
find_inode_fast+0x2b9/0x3c0 fs/inode.c:933
iget_locked+0xb4/0x820 fs/inode.c:1295
__ext4_iget+0x230/0x3d90 fs/ext4/inode.c:4669
ext4_xattr_inode_cache_find fs/ext4/xattr.c:1508 [inline]
ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1543 [inline]
ext4_xattr_set_entry+0x1f90/0x3d30 fs/ext4/xattr.c:1684
ext4_xattr_block_set+0x973/0x2d30 fs/ext4/xattr.c:2004
ext4_xattr_set_handle+0xbd5/0x12b0 fs/ext4/xattr.c:2421
ext4_xattr_set+0x22a/0x320 fs/ext4/xattr.c:2522
__vfs_setxattr+0x3e0/0x420 fs/xattr.c:182
__vfs_setxattr_noperm+0x129/0x5e0 fs/xattr.c:216
vfs_setxattr+0x168/0x2f0 fs/xattr.c:303
do_setxattr fs/xattr.c:588 [inline]
setxattr+0x2da/0x300 fs/xattr.c:611
path_setxattr+0x142/0x280 fs/xattr.c:630
__do_sys_setxattr fs/xattr.c:646 [inline]
__se_sys_setxattr fs/xattr.c:642 [inline]
__x64_sys_setxattr+0xb7/0xd0 fs/xattr.c:642
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fcaa4351ec9
RSP: 002b:00007fcaa2598038 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007fcaa45a9090 RCX: 00007fcaa4351ec9
RDX: 0000200000001400 RSI: 00002000000001c0 RDI: 0000200000000380
RBP: 00007fcaa43d4f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000835 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fcaa45a9128 R14: 00007fcaa45a9090 R15: 00007ffef705e8d8
</TASK>
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/u4:2/154:
#0: ffff8881433f2938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90002057d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff888016a820e0 (&type->s_umount_key#41){.+.+}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
2 locks held by getty/3946:
#0: ffff88802bff1098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900025e62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
3 locks held by kworker/1:13/4534:
#0: ffff888016870938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90003edfd00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff88807c0f8240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x271/0x3240 drivers/net/netdevsim/fib.c:1480
2 locks held by kworker/0:16/6215:
#0: ffff888016872138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90003f7fd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
3 locks held by syz.9.888/8342:
#0: ffff88805f69a460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
#1: ffff88805f3917e0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805f3917e0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: vfs_setxattr+0x141/0x2f0 fs/xattr.c:302
#2: ffff88805f3914b8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline]
#2: ffff88805f3914b8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_set_handle+0x171/0x12b0 fs/ext4/xattr.c:2336
3 locks held by syz.9.888/8350:
#0: ffff88805f69a460 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
#1: ffff88805f3903f0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805f3903f0 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: vfs_setxattr+0x141/0x2f0 fs/xattr.c:302
#2: ffff88805f3900c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline]
#2: ffff88805f3900c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_set_handle+0x171/0x12b0 fs/ext4/xattr.c:2336
1 lock held by syz.5.1148/9442:
#0: ffff88801ffabd18 (&disk->open_mutex){+.+.}-{3:3}, at: sync_bdevs+0x1ab/0x320 block/bdev.c:1053
2 locks held by syz.4.1311/10243:
#0: ffff888061c5ec70 (&fc->uapi_mutex){+.+.}-{3:3}, at: __do_sys_fsconfig fs/fsopen.c:437 [inline]
#0: ffff888061c5ec70 (&fc->uapi_mutex){+.+.}-{3:3}, at: __se_sys_fsconfig+0x5ec/0x750 fs/fsopen.c:314
#1: ffff88801ffabd18 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x157/0xa60 block/bdev.c:820
3 locks held by syz-executor/10773:
#0: ffff888057200ff0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x5f/0x1030 net/bluetooth/hci_core.c:1737
#1: ffff888057200078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_do_close+0x3f4/0x1030 net/bluetooth/hci_core.c:1782
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1517 [inline]
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xa4/0x220 net/bluetooth/hci_conn.c:1622
4 locks held by syz-executor/11756:
3 locks held by syz.0.1621/12083:
#0: ffff888059644ff0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x5f/0x1030 net/bluetooth/hci_core.c:1737
#1: ffff888059644078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_do_close+0x3f4/0x1030 net/bluetooth/hci_core.c:1782
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1517 [inline]
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xa4/0x220 net/bluetooth/hci_conn.c:1622
1 lock held by syz-executor/12461:
#0: ffff88801ffabd18 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_get_by_dev+0x157/0xa60 block/bdev.c:820
1 lock held by rm/12661:
#0: ffff888065e47128 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#0: ffff888065e47128 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15d/0x2b0 mm/util.c:549
4 locks held by syz-executor/12675:
#0: ffff88807691cff0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x5f/0x1030 net/bluetooth/hci_core.c:1737
#1: ffff88807691c078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_do_close+0x3f4/0x1030 net/bluetooth/hci_core.c:1782
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1517 [inline]
#2: ffffffff8d37e7e8 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xa4/0x220 net/bluetooth/hci_conn.c:1622
#3: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#3: ffffffff8c1210e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x347/0x6b0 kernel/rcu/tree_exp.h:845
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 5034 Comm: kworker/u4:14 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:arch_irqs_disabled_flags arch/x86/include/asm/irqflags.h:127 [inline]
RIP: 0010:check_preemption_disabled+0x59/0x110 lib/smp_processor_id.c:19
Code: 48 8b 0c 25 28 00 00 00 48 3b 4c 24 08 0f 85 c4 00 00 00 48 83 c4 10 5b 41 5e 41 5f 5d c3 48 c7 04 24 00 00 00 00 9c 8f 04 24 <f7> 04 24 00 02 00 00 74 cc 65 4c 8b 3d b6 30 59 76 41 f6 47 2f 04
RSP: 0018:ffffc9000346fa88 EFLAGS: 00000046
RAX: 0000000000000001 RBX: ffff88802abf8000 RCX: 0000000080000000
RDX: 0000000000000000 RSI: ffffffff8a0b2620 RDI: ffffffff8a59a4c0
RBP: ffffc9000346fbd0 R08: dffffc0000000000 R09: fffffbfff1ad32b6
R10: fffffbfff1ad32b6 R11: 1ffffffff1ad32b5 R12: 000000000000037c
R13: dffffc0000000000 R14: ffff88802abf8aec R15: 1ffff9200068df64
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3014901e80 CR3: 000000002a703000 CR4: 00000000003506e0
DR0: 0000000000000004 DR1: 0000000000000006 DR2: 0000000000000005
DR3: fffffffffffffff1 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lockdep_recursion_inc kernel/locking/lockdep.c:431 [inline]
lock_release+0x156/0x870 kernel/locking/lockdep.c:5642
rcu_read_unlock include/linux/rcupdate.h:772 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:416 [inline]
batadv_nc_worker+0x25b/0x5c0 net/batman-adv/network-coding.c:723
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages