[v6.6] INFO: task hung in lock_metapage

2 views
Skip to first unread message

syzbot

unread,
Jul 20, 2025, 6:34:35 AM7/20/25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d96eb99e2f0e Linux 6.6.99
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=102684f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bfd82343ac39d3b
dashboard link: https://syzkaller.appspot.com/bug?extid=4e40ac4f0b1f7535cc05
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/11b332f11d00/disk-d96eb99e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8a063193b98f/vmlinux-d96eb99e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b36214b822e5/bzImage-d96eb99e.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4e40ac...@syzkaller.appspotmail.com

INFO: task jfsCommit:112 blocked for more than 143 seconds.
Not tainted 6.6.99-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit state:D stack:27272 pid:112 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x14e2/0x4580 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
io_schedule+0x80/0xd0 kernel/sched/core.c:9023
__lock_metapage fs/jfs/jfs_metapage.c:50 [inline]
lock_metapage+0x1ec/0x310 fs/jfs/jfs_metapage.c:64
__get_metapage+0x4ca/0xfa0 fs/jfs/jfs_metapage.c:639
diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
diFree+0x978/0x2c10 fs/jfs/jfs_imap.c:959
jfs_evict_inode+0x32b/0x440 fs/jfs/inode.c:156
evict+0x486/0x870 fs/inode.c:705
txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
jfs_lazycommit+0x42b/0xa60 fs/jfs/jfs_txnmgr.c:2732
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8cd2fba0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8cd2fba0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8cd2fba0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by jfsCommit/111:
#0: ffff888074da0920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2a0/0x2c10 fs/jfs/jfs_imap.c:889
#1: ffff88805dcf4b38 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2be/0x2c10 fs/jfs/jfs_imap.c:894
2 locks held by jfsCommit/112:
#0: ffff888059c88920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2a0/0x2c10 fs/jfs/jfs_imap.c:889
#1: ffff8880588b38b8 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2be/0x2c10 fs/jfs/jfs_imap.c:894
2 locks held by getty/5555:
#0: ffff88802d5c20a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000326e2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x425/0x1380 drivers/tty/n_tty.c:2217
2 locks held by syz-executor/5784:
#0: ffff888025cbe0e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff888025cbe0e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff888025cbe0e0 (&type->s_umount_key#65){++++}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6368:
#0: ffff88807fa920e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807fa920e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807fa920e0 (&type->s_umount_key#65){++++}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/7658:
#0: ffff8880306300e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff8880306300e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff8880306300e0 (&type->s_umount_key#65){++++}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
4 locks held by syz.0.244/7943:
#0: ffff8880247befc8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2a3/0x330 fs/file.c:1042
#1: ffff888078f70418 (sb_writers#19){.+.+}-{0:0}, at: vfs_write+0x20e/0x940 fs/read_write.c:580
#2: ffff888077d8bd10 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
#2: ffff888077d8bd10 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: jfs_fsync+0x98/0x1b0 fs/jfs/file.c:28
#3: ffff888077d8b948 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x1cb/0x520 fs/jfs/inode.c:102
2 locks held by syz-executor/8205:
#0: ffff888026cc20e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff888026cc20e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff888026cc20e0 (&type->s_umount_key#65){++++}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
1 lock held by syz-executor/8290:
#0: ffff888053b920e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff888053b920e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff888053b920e0 (&type->s_umount_key#65){++++}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
2 locks held by syz-executor/8404:
#0: ffff8880539980e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff8880539980e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff8880539980e0 (&type->s_umount_key#65){++++}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
1 lock held by syz-executor/8846:
#0: ffffffff8cd35b78 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
#0: ffffffff8cd35b78 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x448/0x830 kernel/rcu/tree_exp.h:1004
1 lock held by syz-executor/8905:
#0: ffff88801d3ce0e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88801d3ce0e0 (&type->s_umount_key#65){++++}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88801d3ce0e0 (&type->s_umount_key#65){++++}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
2 locks held by kworker/0:8/9052:
#0: ffff888017872538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff888017872538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#1: ffffc900036b7d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc900036b7d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
2 locks held by rm/9941:
#0: ffff8880b8e3c458 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2a/0x140 kernel/sched/core.c:558
#1: ffff8880b8e288c8 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x39c/0x6d0 kernel/sched/psi.c:998

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

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted 6.6.99-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x39b/0x3d0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf41/0xf80 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 9947 Comm: sed Not tainted 6.6.99-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:next_tid mm/slub.c:2437 [inline]
RIP: 0010:__update_cpu_freelist_fast mm/slub.c:3043 [inline]
RIP: 0010:__slab_alloc_node mm/slub.c:3400 [inline]
RIP: 0010:slab_alloc_node mm/slub.c:3475 [inline]
RIP: 0010:slab_alloc mm/slub.c:3493 [inline]
RIP: 0010:__kmem_cache_alloc_lru mm/slub.c:3500 [inline]
RIP: 0010:kmem_cache_alloc+0xa3/0x2e0 mm/slub.c:3509
Code: 48 03 05 a8 1c 26 7e 48 8b 78 08 4c 8b 38 4d 85 ff 0f 84 eb 00 00 00 48 83 78 10 00 0f 84 e0 00 00 00 41 8b 45 28 4a 8b 1c 38 <48> 8d 4f 08 4d 8b 45 00 48 89 fa 4c 89 f8 65 49 0f c7 08 0f 1f 00
RSP: 0018:ffffc90004b9f8d8 EFLAGS: 00000282
RAX: 0000000000000028 RBX: ffff888068aa1960 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000058 RDI: 000000000009cbf0
RBP: 0000000000000dc0 R08: ffffffff8e4a7cef R09: 1ffffffff1c94f9d
R10: dffffc0000000000 R11: fffffbfff1c94f9e R12: 0000000000000058
R13: ffff888019a4d280 R14: ffff888019a4d280 R15: ffff888068aa18e8
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f941596f420 CR3: 000000005283f000 CR4: 00000000003506f0
Call Trace:
<TASK>
kmem_cache_zalloc include/linux/slab.h:711 [inline]
lsm_file_alloc security/security.c:612 [inline]
security_file_alloc+0x34/0x120 security/security.c:2603
init_file+0x94/0x1f0 fs/file_table.c:161
alloc_empty_file+0xb7/0x1d0 fs/file_table.c:210
path_openat+0x100/0x3190 fs/namei.c:3775
do_filp_open+0x1c5/0x3d0 fs/namei.c:3816
do_sys_openat2+0x12c/0x1c0 fs/open.c:1419
do_sys_open fs/open.c:1434 [inline]
__do_sys_openat fs/open.c:1450 [inline]
__se_sys_openat fs/open.c:1445 [inline]
__x64_sys_openat+0x139/0x160 fs/open.c:1445
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f941598e0ba
Code: 41 89 f2 48 89 54 24 e0 41 83 e2 40 75 2a 89 f0 f7 d0 a9 00 00 41 00 74 1f 89 f2 b8 01 01 00 00 48 89 fe bf 9c ff ff ff 0f 05 <48> 3d 00 f0 ff ff 77 2e c3 0f 1f 44 00 00 48 8d 44 24 08 c7 44 24
RSP: 002b:00007ffecef82068 EFLAGS: 00000206 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 000055d895915534 RCX: 00007f941598e0ba
RDX: 0000000000080000 RSI: 00007f9415996134 RDI: 00000000ffffff9c
RBP: 00007f94159a1bf8 R08: 0000000000000000 R09: 000055d895915534
R10: 0000000000000000 R11: 0000000000000206 R12: ffffffffffffffff
R13: 0000000000000001 R14: 00007f94159a1000 R15: 00007f94159a2700
</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

unread,
Jul 20, 2025, 1:47:36 PM7/20/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: d96eb99e2f0e Linux 6.6.99
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=148c638c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bfd82343ac39d3b
dashboard link: https://syzkaller.appspot.com/bug?extid=4e40ac4f0b1f7535cc05
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1548f7d4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=168f4b82580000
mounted in repro: https://storage.googleapis.com/syzbot-assets/b0d12a6bad66/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=128f4b82580000)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4e40ac...@syzkaller.appspotmail.com

INFO: task jfsCommit:111 blocked for more than 143 seconds.
Not tainted 6.6.99-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit state:D stack:26864 pid:111 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x14e2/0x4580 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
io_schedule+0x80/0xd0 kernel/sched/core.c:9023
__lock_metapage fs/jfs/jfs_metapage.c:50 [inline]
lock_metapage+0x1ec/0x310 fs/jfs/jfs_metapage.c:64
__get_metapage+0x4ca/0xfa0 fs/jfs/jfs_metapage.c:639
diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
diFree+0x978/0x2c10 fs/jfs/jfs_imap.c:959
jfs_evict_inode+0x32b/0x440 fs/jfs/inode.c:156
evict+0x486/0x870 fs/inode.c:705
txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
jfs_lazycommit+0x42b/0xa60 fs/jfs/jfs_txnmgr.c:2732
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
INFO: task jfsCommit:112 blocked for more than 144 seconds.
Not tainted 6.6.99-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit state:D stack:27120 pid:112 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5381 [inline]
__schedule+0x14e2/0x4580 kernel/sched/core.c:6700
schedule+0xbd/0x170 kernel/sched/core.c:6774
io_schedule+0x80/0xd0 kernel/sched/core.c:9023
__lock_metapage fs/jfs/jfs_metapage.c:50 [inline]
lock_metapage+0x1ec/0x310 fs/jfs/jfs_metapage.c:64
__get_metapage+0x4ca/0xfa0 fs/jfs/jfs_metapage.c:639
diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
diFree+0x978/0x2c10 fs/jfs/jfs_imap.c:959
jfs_evict_inode+0x32b/0x440 fs/jfs/inode.c:156
evict+0x486/0x870 fs/inode.c:705
txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
jfs_lazycommit+0x42b/0xa60 fs/jfs/jfs_txnmgr.c:2732
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>

Showing all locks held in the system:
1 lock held by ksoftirqd/1/22:
1 lock held by khungtaskd/29:
#0: ffffffff8cd2fba0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8cd2fba0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8cd2fba0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by jfsCommit/111:
#0: ffff88807be80920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2a0/0x2c10 fs/jfs/jfs_imap.c:889
#1: ffff88805cb22638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2be/0x2c10 fs/jfs/jfs_imap.c:894
2 locks held by jfsCommit/112:
#0: ffff88807d848920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2a0/0x2c10 fs/jfs/jfs_imap.c:889
#1: ffff88805cb266f8 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2be/0x2c10 fs/jfs/jfs_imap.c:894
4 locks held by kworker/u4:6/1081:
#0: ffff888019e6ad38 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff888019e6ad38 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#1: ffff8880b8e288c8 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x39c/0x6d0 kernel/sched/psi.c:998
#2: ffff8880b8e297d8 (&base->lock){-.-.}-{2:2}, at: lock_timer_base+0x123/0x270 kernel/time/timer.c:999
#3: ffffffff9705f298 (&obj_hash[i].lock){-.-.}-{2:2}, at: debug_object_activate+0x6c/0x4b0 lib/debugobjects.c:709
3 locks held by kworker/u5:1/5103:
#0: ffff8880605cb538 ((wq_completion)hci3){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff8880605cb538 ((wq_completion)hci3){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#1: ffffc900101bfd00 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc900101bfd00 ((work_completion)(&hdev->cmd_sync_work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#2: ffff88807c120e70 (&hdev->req_lock){+.+.}-{3:3}, at: hci_cmd_sync_work+0x1d4/0x390 net/bluetooth/hci_sync.c:326
2 locks held by getty/5554:
#0: ffff88803294a0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x425/0x1380 drivers/tty/n_tty.c:2217
2 locks held by kworker/1:4/5886:
#0: ffff888017872538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff888017872538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#1: ffffc90002e77d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc90002e77d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
2 locks held by syz-executor/5906:
#0: ffff88807ccae0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807ccae0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807ccae0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/5911:
#0: ffff88807e0e60e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807e0e60e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807e0e60e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/5912:
#0: ffff8881423440e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff8881423440e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff8881423440e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6302:
#0: ffff88807cef20e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807cef20e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807cef20e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6332:
#0: ffff88807e72e0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807e72e0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807e72e0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6334:
#0: ffff88802c94c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88802c94c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88802c94c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6336:
#0: ffff88807a51c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807a51c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807a51c0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by syz-executor/6724:
#0: ffff8880233ba0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff8880233ba0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff8880233ba0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffffffff8d148588 (jfs_log_mutex){+.+.}-{3:3}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1444
2 locks held by dhcpcd/6754:
#0: ffff88805cadf420 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
#0: ffff88805cadf420 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: __sock_release net/socket.c:658 [inline]
#0: ffff88805cadf420 (&sb->s_type->i_mutex_key#10){+.+.}-{3:3}, at: sock_close+0x9b/0x230 net/socket.c:1421
#1: ffffffff8cd35b78 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:292 [inline]
#1: ffffffff8cd35b78 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x448/0x830 kernel/rcu/tree_exp.h:1004
1 lock held by syz-executor/6795:
#0: ffff8880759aa0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff8880759aa0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff8880759aa0e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
1 lock held by syz-executor/6816:
#0: ffff88807e0180e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807e0180e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807e0180e0 (&type->s_umount_key#56){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
1 lock held by udevd/6830:
1 lock held by syz.4.269/7980:
2 locks held by syz.2.270/7985:

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

NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted 6.6.99-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x39b/0x3d0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf41/0xf80 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 1146 Comm: kworker/u4:10 Not tainted 6.6.99-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: events_unbound nsim_dev_trap_report_work
RIP: 0010:unwind_done arch/x86/include/asm/unwind.h:50 [inline]
RIP: 0010:unwind_next_frame+0xa6/0x2970 arch/x86/kernel/unwind_orc.c:475
Code: 00 00 4c 89 e3 48 c1 eb 03 42 0f b6 04 2b 84 c0 0f 85 df 21 00 00 41 8b 2c 24 31 ff 89 ee e8 81 f6 4a 00 89 ac 24 8c 00 00 00 <85> ed 74 77 4c 89 74 24 60 48 89 5c 24 18 bf 01 00 00 00 e8 d2 ce
RSP: 0000:ffffc9000471f4f0 EFLAGS: 00000293
RAX: ffffffff813aa35f RBX: 1ffff920008e3ec5 RCX: 0000000000000000
RDX: ffff888023988000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffffc9000471f601 R09: 0000000000000000
R10: ffffc9000471f628 R11: fffff520008e3ed1 R12: ffffc9000471f628
R13: dffffc0000000000 R14: ffffc9000471f660 R15: ffffffff813ad3e2
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f86751af000 CR3: 000000005d3fd000 CR4: 00000000003506e0
Call Trace:
<TASK>
__unwind_start+0x66a/0x7e0 arch/x86/kernel/unwind_orc.c:760
unwind_start arch/x86/include/asm/unwind.h:64 [inline]
arch_stack_walk+0xf8/0x190 arch/x86/kernel/stacktrace.c:24
stack_trace_save+0x9c/0xe0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4e/0x70 mm/kasan/common.c:52
__kasan_slab_alloc+0x6c/0x80 mm/kasan/common.c:328
kasan_slab_alloc include/linux/kasan.h:188 [inline]
slab_post_alloc_hook+0x6e/0x4d0 mm/slab.h:767
slab_alloc_node mm/slub.c:3485 [inline]
kmem_cache_alloc_node+0x150/0x330 mm/slub.c:3530
__alloc_skb+0x108/0x2c0 net/core/skbuff.c:640
alloc_skb include/linux/skbuff.h:1284 [inline]
nsim_dev_trap_skb_build drivers/net/netdevsim/dev.c:748 [inline]
nsim_dev_trap_report drivers/net/netdevsim/dev.c:805 [inline]
nsim_dev_trap_report_work+0x293/0xb00 drivers/net/netdevsim/dev.c:851
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
Reply all
Reply to author
Forward
0 new messages