syzbot


INFO: task hung in process_measurement (3)

Status: upstream: reported on 2025/05/07 00:26
Reported-by: syzbot+7253e80eb0ac03a1ccda@syzkaller.appspotmail.com
First crash: 54d, last: 54d
Similar bugs (11)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 INFO: task hung in process_measurement (2) 1 171d 171d 0/3 auto-obsoleted due to no activity on 2025/04/20 01:13
linux-5.15 INFO: task hung in process_measurement 1 707d 707d 0/3 auto-obsoleted due to no activity on 2023/10/31 09:35
upstream INFO: task hung in process_measurement (3) lsm integrity C done 12 30m 39d 0/29 upstream: reported C repro on 2025/05/21 17:47
linux-4.19 INFO: task hung in process_measurement 2 2038d 2113d 0/1 auto-closed as invalid on 2020/03/29 20:33
upstream INFO: task hung in process_measurement integrity lsm C done inconclusive 52 1432d 2463d 0/29 closed as invalid on 2022/02/08 10:56
upstream INFO: task hung in process_measurement (2) integrity lsm C done 607 56d 659d 28/29 fixed on 2025/05/06 15:33
linux-4.19 INFO: task hung in process_measurement (3) 5 845d 850d 0/1 upstream: reported on 2023/03/02 09:48
linux-4.14 INFO: task hung in process_measurement 3 1933d 1989d 0/1 auto-closed as invalid on 2020/07/13 00:59
linux-6.1 INFO: task hung in process_measurement 39 349d 358d 0/3 auto-obsoleted due to no activity on 2024/09/23 07:47
linux-5.15 INFO: task hung in process_measurement (2) 97 249d 359d 0/3 auto-obsoleted due to no activity on 2025/01/01 08:25
linux-4.19 INFO: task hung in process_measurement (2) 1 1707d 1707d 0/1 auto-closed as invalid on 2021/02/23 17:00

Sample crash report:
INFO: task syz.3.123:5183 blocked for more than 143 seconds.
      Not tainted 5.15.181-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.123       state:D stack:27632 pid: 5183 ppid:  4175 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5030 [inline]
 __schedule+0x11b8/0x43b0 kernel/sched/core.c:6376
 schedule+0x11b/0x1e0 kernel/sched/core.c:6459
 rwsem_down_write_slowpath+0xc46/0x11f0 kernel/locking/rwsem.c:1165
 inode_lock include/linux/fs.h:787 [inline]
 process_measurement+0x33d/0x1a10 security/integrity/ima/ima_main.c:242
 ima_file_check+0xc1/0x100 security/integrity/ima/ima_main.c:533
 do_open fs/namei.c:3610 [inline]
 path_openat+0x2735/0x2f30 fs/namei.c:3742
 do_filp_open+0x1b3/0x3e0 fs/namei.c:3769
 do_sys_openat2+0x142/0x4a0 fs/open.c:1253
 do_sys_open fs/open.c:1269 [inline]
 __do_sys_creat fs/open.c:1345 [inline]
 __se_sys_creat fs/open.c:1339 [inline]
 __x64_sys_creat+0x8c/0xb0 fs/open.c:1339
 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:0x7f164f4f2969
RSP: 002b:00007f164d339038 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f164f71a080 RCX: 00007f164f4f2969
RDX: 0000000000000000 RSI: d931d3864d39dcca RDI: 0000200000000100
RBP: 00007f164f574ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f164f71a080 R15: 00007fffb3db6308
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8c11be60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
4 locks held by kworker/u4:1/144:
 #0: ffff888018d98938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc9000166fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
 #2: ffff8880617d40e0 (&type->s_umount_key#55){++++}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
 #3: ffff88802a5551b0 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x47d/0x660 fs/f2fs/segment.c:528
2 locks held by getty/3933:
 #0: ffff88807f091098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002cd62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
2 locks held by kworker/0:6/4212:
 #0: ffff888016872138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc900030dfd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
7 locks held by syz.3.123/5146:
2 locks held by syz.3.123/5183:
 #0: ffff8880617d4460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
 #1: ffff88805e53ba50 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #1: ffff88805e53ba50 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: process_measurement+0x33d/0x1a10 security/integrity/ima/ima_main.c:242
1 lock held by syz.7.677/7683:
 #0: ffff888074535c10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #0: ffff888074535c10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline]
 #0: ffff888074535c10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1336
1 lock held by dhcpcd/7737:
 #0: ffff88801c260210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #0: ffff88801c260210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline]
 #0: ffff88801c260210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1336
2 locks held by dhcpcd/7738:
 #0: ffff88801c260e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #0: ffff88801c260e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline]
 #0: ffff88801c260e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1336
 #1: ffffffff8c1208e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
 #1: ffffffff8c1208e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.181-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/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: 4221 Comm: kworker/u4:5 Not tainted 5.15.181-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:check_region_inline mm/kasan/generic.c:-1 [inline]
RIP: 0010:kasan_check_range+0x30/0x290 mm/kasan/generic.c:189
Code: 84 a4 01 00 00 41 57 41 56 53 49 89 f8 49 01 f0 0f 82 57 02 00 00 49 89 f8 49 c1 e8 2f 41 81 f8 ff ff 01 00 0f 82 43 02 00 00 <49> bf 01 00 00 00 00 fc ff df 49 89 fb 49 c1 eb 03 49 b8 00 00 00
RSP: 0018:ffffc9000316f800 EFLAGS: 00000046
RAX: 0000000000000001 RBX: 0000000000000015 RCX: ffffffff815bf989
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8ff990c0
RBP: ffffc9000316fa70 R08: 000000000001ffff R09: fffffbfff1ff3236
R10: fffffbfff1ff3236 R11: 1ffffffff1ff3235 R12: 00000000ac97705a
R13: ffff888029d49dc0 R14: 00000000583408ea R15: ffff888029d4a920
FS:  0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6cafb1eab8 CR3: 0000000028a2e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 instrument_atomic_read include/linux/instrumented.h:71 [inline]
 test_bit include/asm-generic/bitops/instrumented-non-atomic.h:134 [inline]
 hlock_class kernel/locking/lockdep.c:197 [inline]
 __lock_acquire+0x12d9/0x7c60 kernel/locking/lockdep.c:5009
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:312
 rcu_read_lock include/linux/rcupdate.h:739 [inline]
 batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:412 [inline]
 batadv_nc_worker+0xc9/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>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/05/07 00:26 linux-5.15.y 16fdf2c7111b 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in process_measurement
* Struck through repros no longer work on HEAD.