syzbot


INFO: task hung in restrict_one_thread_callback

Status: upstream: reported C repro on 2026/02/20 11:11
Subsystems: lsm kernel
[Documentation on labels]
Reported-by: syzbot+7ea2f5e9dfd468201817@syzkaller.appspotmail.com
Fix commit: landlock: Serialize TSYNC thread restriction
Patched on: [ci-upstream-linux-next-kasan-gce-root ci-upstream-rust-kasan-gce], missing on: [ci-qemu-gce-upstream-auto ci-qemu-native-arm64-kvm ci-qemu-upstream ci-qemu-upstream-386 ci-qemu2-arm32 ci-qemu2-arm64 ci-qemu2-arm64-compat ci-qemu2-arm64-mte ci-qemu2-riscv64 ci-snapshot-upstream-root ci-upstream-bpf-kasan-gce ci-upstream-bpf-next-kasan-gce ci-upstream-gce-arm64 ci-upstream-gce-leak ci-upstream-kasan-badwrites-root ci-upstream-kasan-gce ci-upstream-kasan-gce-386 ci-upstream-kasan-gce-root ci-upstream-kasan-gce-selinux-root ci-upstream-kasan-gce-smack-root ci-upstream-kmsan-gce-386-root ci-upstream-kmsan-gce-root ci-upstream-net-kasan-gce ci-upstream-net-this-kasan-gce ci2-upstream-fs ci2-upstream-kcsan-gce ci2-upstream-usb]
First crash: 29d, last: 1d14h
Discussions (10)
Title Replies (including bot) Last reply
[PATCH v5 0/2] landlock: Fix TSYNC deadlock and clean up error path 5 (5) 2026/03/06 07:00
[PATCH v4 1/2] landlock: Serialize TSYNC thread restriction 3 (3) 2026/03/04 19:05
[PATCH v3 0/2] landlock: Fix TSYNC deadlock and clean up error path 17 (17) 2026/03/04 14:08
[PATCH v4 2/2] landlock: Clean up interrupted thread logic in TSYNC 1 (1) 2026/03/04 09:54
[PATCH v4 0/2] landlock: Fix TSYNC deadlock and clean up error path 1 (1) 2026/03/04 09:54
[syzbot] [kernel?] INFO: task hung in restrict_one_thread_callback 11 (24) 2026/02/27 01:49
[PATCH v3 0/2] landlock: Fix TSYNC deadlock and clean up error path 1 (1) 2026/02/26 01:52
[PATCH v3 0/2] landlock: Fix TSYNC deadlock and clean up error path 1 (1) 2026/02/26 01:51
[PATCH v2 0/2] landlock: Fix TSYNC deadlock and clean up error path 7 (7) 2026/02/26 01:43
[PATCH] landlock: Fix deadlock in restrict_one_thread_callback 2 (2) 2026/02/24 08:48
Last patch testing requests (11)
Created Duration User Patch Repo Result
2026/02/27 00:03 46m hdanton@sina.com patch upstream OK log
2026/02/26 10:05 39m hdanton@sina.com patch upstream OK log
2026/02/26 02:19 24m hdanton@sina.com patch upstream report log
2026/02/25 22:33 1h24m hdanton@sina.com patch upstream report log
2026/02/25 12:21 1h51m hdanton@sina.com patch upstream report log
2026/02/25 10:23 21m hdanton@sina.com upstream report log
2026/02/25 05:10 17m hdanton@sina.com patch linux-next error
2026/02/24 04:25 30m dingyihan@uniontech.com patch git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 635c467cc14e OK log
2026/02/24 03:17 22m dingyihan@uniontech.com patch linux-next error
2026/02/24 00:10 36m hdanton@sina.com patch linux-next error
2026/02/21 06:27 32m dingyihan@uniontech.com patch linux-next OK log

Sample crash report:
INFO: task syz.3.10487:27834 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.10487     state:D stack:25152 pid:27834 tgid:27834 ppid:25794  task_flags:0x400040 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5295 [inline]
 __schedule+0x15dd/0x52d0 kernel/sched/core.c:6908
 __schedule_loop kernel/sched/core.c:6990 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:7005
 schedule_timeout+0xc3/0x2c0 kernel/time/sleep_timeout.c:75
 do_wait_for_common kernel/sched/completion.c:100 [inline]
 __wait_for_common kernel/sched/completion.c:121 [inline]
 wait_for_common kernel/sched/completion.c:132 [inline]
 wait_for_completion+0x2cc/0x5e0 kernel/sched/completion.c:153
 restrict_one_thread security/landlock/tsync.c:128 [inline]
 restrict_one_thread_callback+0x320/0x570 security/landlock/tsync.c:162
 task_work_run+0x1d9/0x270 kernel/task_work.c:233
 get_signal+0x11eb/0x1330 kernel/signal.c:2807
 arch_do_signal_or_restart+0xbc/0x830 arch/x86/kernel/signal.c:337
 __exit_to_user_mode_loop kernel/entry/common.c:64 [inline]
 exit_to_user_mode_loop+0x86/0x480 kernel/entry/common.c:98
 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]
 syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:325 [inline]
 do_syscall_64+0x32d/0xf80 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0efdb5cfce
RSP: 002b:00007ffcc0851e18 EFLAGS: 00000246 ORIG_RAX: 00000000000000db
RAX: fffffffffffffdfc RBX: 00005555900b6500 RCX: 00007f0efdb5cfce
RDX: 00007ffcc0851e70 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007f0efde17da0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000095750
R13: 00007f0efde1618c R14: 00000000000954c4 R15: 00007f0efde16180
 </TASK>
INFO: task syz.3.10487:27836 blocked for more than 144 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.10487     state:D stack:23424 pid:27836 tgid:27834 ppid:25794  task_flags:0x400140 flags:0x00080006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5295 [inline]
 __schedule+0x15dd/0x52d0 kernel/sched/core.c:6908
 __schedule_loop kernel/sched/core.c:6990 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:7005
 schedule_timeout+0xc3/0x2c0 kernel/time/sleep_timeout.c:75
 do_wait_for_common kernel/sched/completion.c:100 [inline]
 __wait_for_common kernel/sched/completion.c:121 [inline]
 wait_for_common kernel/sched/completion.c:132 [inline]
 wait_for_completion+0x2cc/0x5e0 kernel/sched/completion.c:153
 landlock_restrict_sibling_threads+0xe9c/0x11f0 security/landlock/tsync.c:539
 __do_sys_landlock_restrict_self security/landlock/syscalls.c:574 [inline]
 __se_sys_landlock_restrict_self+0x540/0x810 security/landlock/syscalls.c:482
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0efdb9c799
RSP: 002b:00007f0efe9c2028 EFLAGS: 00000246 ORIG_RAX: 00000000000001be
RAX: ffffffffffffffda RBX: 00007f0efde15fa0 RCX: 00007f0efdb9c799
RDX: 0000000000000000 RSI: 000000000000000e RDI: 0000000000000003
RBP: 00007f0efdc32bd9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f0efde16038 R14: 00007f0efde15fa0 R15: 00007ffcc0851d38
 </TASK>
INFO: task syz.3.10487:27842 blocked for more than 144 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.10487     state:D stack:28504 pid:27842 tgid:27834 ppid:25794  task_flags:0x400140 flags:0x00080006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5295 [inline]
 __schedule+0x15dd/0x52d0 kernel/sched/core.c:6908
 __schedule_loop kernel/sched/core.c:6990 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:7005
 schedule_timeout+0xc3/0x2c0 kernel/time/sleep_timeout.c:75
 do_wait_for_common kernel/sched/completion.c:100 [inline]
 __wait_for_common kernel/sched/completion.c:121 [inline]
 wait_for_common kernel/sched/completion.c:132 [inline]
 wait_for_completion+0x2cc/0x5e0 kernel/sched/completion.c:153
 landlock_restrict_sibling_threads+0xe9c/0x11f0 security/landlock/tsync.c:539
 __do_sys_landlock_restrict_self security/landlock/syscalls.c:574 [inline]
 __se_sys_landlock_restrict_self+0x540/0x810 security/landlock/syscalls.c:482
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0efdb9c799
RSP: 002b:00007f0efe9a1028 EFLAGS: 00000246 ORIG_RAX: 00000000000001be
RAX: ffffffffffffffda RBX: 00007f0efde16090 RCX: 00007f0efdb9c799
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 0000000000000003
RBP: 00007f0efdc32bd9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f0efde16128 R14: 00007f0efde16090 R15: 00007ffcc0851d38
 </TASK>
INFO: task syz.3.10487:27847 blocked for more than 145 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.10487     state:D stack:27688 pid:27847 tgid:27834 ppid:25794  task_flags:0x400040 flags:0x00080002
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5295 [inline]
 __schedule+0x15dd/0x52d0 kernel/sched/core.c:6908
 __schedule_loop kernel/sched/core.c:6990 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:7005
 schedule_timeout+0xc3/0x2c0 kernel/time/sleep_timeout.c:75
 do_wait_for_common kernel/sched/completion.c:100 [inline]
 __wait_for_common kernel/sched/completion.c:121 [inline]
 wait_for_common kernel/sched/completion.c:132 [inline]
 wait_for_completion+0x2cc/0x5e0 kernel/sched/completion.c:153
 restrict_one_thread security/landlock/tsync.c:128 [inline]
 restrict_one_thread_callback+0x320/0x570 security/landlock/tsync.c:162
 task_work_run+0x1d9/0x270 kernel/task_work.c:233
 get_signal+0x11eb/0x1330 kernel/signal.c:2807
 arch_do_signal_or_restart+0xbc/0x830 arch/x86/kernel/signal.c:337
 __exit_to_user_mode_loop kernel/entry/common.c:64 [inline]
 exit_to_user_mode_loop+0x86/0x480 kernel/entry/common.c:98
 __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]
 syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]
 syscall_exit_to_user_mode include/linux/entry-common.h:325 [inline]
 do_syscall_64+0x32d/0xf80 arch/x86/entry/syscall_64.c:100
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f0efdb9c799
RSP: 002b:00007f0efe9800e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007f0efde16188 RCX: 00007f0efdb9c799
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f0efde16188
RBP: 00007f0efde16180 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f0efde16218 R14: 00007ffcc0851c50 R15: 00007ffcc0851d38
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/30:
 #0: ffffffff8e7602e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:312 [inline]
 #0: ffffffff8e7602e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:850 [inline]
 #0: ffffffff8e7602e0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
3 locks held by kworker/u8:5/130:
 #0: ffff88803180b148 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3250 [inline]
 #0: ffff88803180b148 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x9ea/0x1830 kernel/workqueue.c:3358
 #1: ffffc90002e27c40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3251 [inline]
 #1: ffffc90002e27c40 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0xa25/0x1830 kernel/workqueue.c:3358
 #2: ffffffff8fbceac8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #2: ffffffff8fbceac8 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_dad_work+0x11e/0x14c0 net/ipv6/addrconf.c:4198
1 lock held by udevd/5194:
2 locks held by getty/5583:
 #0: ffff888031ba60a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000332b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x45c/0x13c0 drivers/tty/n_tty.c:2211
8 locks held by syz-executor/5508:
 #0: ffff888035532420 (sb_writers#7){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2710 [inline]
 #0: ffff888035532420 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x227/0xb90 fs/read_write.c:684
 #1: ffff88805e0fd088 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1de/0x540 fs/kernfs/file.c:343
 #2: ffff888028361c38 (kn->active#58){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
 #2: ffff888028361c38 (kn->active#58){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x231/0x540 fs/kernfs/file.c:344
 #3: ffffffff8f443428 (nsim_bus_dev_list_lock){+.+.}-{4:4}, at: del_device_store+0xd7/0x370 drivers/net/netdevsim/bus.c:234
 #4: ffff888029eae0e8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:895 [inline]
 #4: ffff888029eae0e8 (&dev->mutex){....}-{4:4}, at: __device_driver_lock drivers/base/dd.c:1106 [inline]
 #4: ffff888029eae0e8 (&dev->mutex){....}-{4:4}, at: device_release_driver_internal+0xb6/0x860 drivers/base/dd.c:1304
 #5: ffff888029eac250 (&devlink->lock_key#24){+.+.}-{4:4}, at: nsim_drv_remove+0x50/0x170 drivers/net/netdevsim/dev.c:1778
 #6: ffffffff8fbceac8 (rtnl_mutex){+.+.}-{4:4}, at: nsim_destroy+0xed/0x680 drivers/net/netdevsim/netdev.c:1177
 #7: ffffffff8e766578 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:311 [inline]
 #7: ffffffff8e766578 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x2d0/0x770 kernel/rcu/tree_exp.h:961
2 locks held by dhcpcd/6574:
 #0: ffff888053fdc260 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1709 [inline]
 #0: ffff888053fdc260 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x33/0xe10 net/packet/af_packet.c:3197
 #1: ffffffff8e766578 (rcu_state.exp_mutex){+.+.}-{4:4}, at: exp_funnel_lock kernel/rcu/tree_exp.h:343 [inline]
 #1: ffffffff8e766578 (rcu_state.exp_mutex){+.+.}-{4:4}, at: synchronize_rcu_expedited+0x38d/0x770 kernel/rcu/tree_exp.h:961
2 locks held by syz.1.15686/6637:
1 lock held by syz.0.15691/6639:
 #0: ffff8880b873ade0 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x31/0x150 kernel/sched/core.c:647

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 30 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x274/0x2d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:161 [inline]
 __sys_info lib/sys_info.c:157 [inline]
 sys_info+0x135/0x170 lib/sys_info.c:165
 check_hung_uninterruptible_tasks kernel/hung_task.c:346 [inline]
 watchdog+0xfd9/0x1030 kernel/hung_task.c:515
 kthread+0x388/0x470 kernel/kthread.c:436
 ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 6655 Comm: syz.4.15698 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
RIP: 0010:cr4_update_pce_mm arch/x86/mm/tlb.c:755 [inline]
RIP: 0010:switch_mm_irqs_off+0x4b8/0x690 arch/x86/mm/tlb.c:969
Code: b3 10 0a 00 00 4c 89 f7 be 04 00 00 00 e8 c0 84 b7 00 4c 89 f0 48 c1 e8 03 42 0f b6 04 28 84 c0 0f 85 ea 00 00 00 41 83 3e 00 <74> 22 e8 51 ea bb ff bf 00 01 00 00 31 f6 eb 1b 48 83 c4 18 5b 41
RSP: 0018:ffffc90004ab7790 EFLAGS: 00000046
RAX: 0000000000000000 RBX: ffff888033706200 RCX: ffffffff81785a60
RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffff888033706c10
RBP: ffff88807d490000 R08: ffff888033706c13 R09: 1ffff110066e0d82
R10: dffffc0000000000 R11: ffffed10066e0d83 R12: 00000000000008c0
R13: dffffc0000000000 R14: ffff888033706c10 R15: 0000000000010000
FS:  00007f80d0f896c0(0000) GS:ffff888125561000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000058 CR3: 0000000065bbe000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5274 [inline]
 __schedule+0x1114/0x52d0 kernel/sched/core.c:6908
 __schedule_loop kernel/sched/core.c:6990 [inline]
 schedule+0x164/0x360 kernel/sched/core.c:7005
 futex_do_wait kernel/futex/waitwake.c:358 [inline]
 __futex_wait+0x1ee/0x420 kernel/futex/waitwake.c:687
 futex_wait+0x119/0x380 kernel/futex/waitwake.c:715
 do_futex+0x333/0x420 kernel/futex/syscalls.c:130
 __do_sys_futex kernel/futex/syscalls.c:207 [inline]
 __se_sys_futex+0x3a8/0x450 kernel/futex/syscalls.c:188
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f80d019c799
Code: Unable to access opcode bytes at 0x7f80d019c76f.
RSP: 002b:00007f80d0f890e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: ffffffffffffffda RBX: 00007f80d0415fa8 RCX: 00007f80d019c799
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f80d0415fa8
RBP: 00007f80d0415fa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f80d0416038 R14: 00007fffbd75e670 R15: 00007fffbd75e758
 </TASK>

Crashes (34):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/03/07 13:06 upstream 651690480a96 5cb44a80 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/02/16 10:56 linux-next 635c467cc14e 1e62d198 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/15 16:53 upstream 267594792a71 ee8d34d6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/13 17:57 upstream 0257f64bdac7 351cb5cf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/12 03:55 upstream b29fb8829bff 2d88ab01 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in restrict_one_thread_callback
2026/03/12 03:10 upstream b29fb8829bff 2d88ab01 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/11 22:59 upstream b29fb8829bff 2d88ab01 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/11 22:45 upstream b29fb8829bff 2d88ab01 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/10 23:11 upstream 1f318b96cc84 4683d576 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/10 21:43 upstream 1f318b96cc84 4683d576 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/10 11:23 upstream 1f318b96cc84 6972f302 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/10 11:08 upstream 1f318b96cc84 6972f302 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/10 07:41 upstream 1f318b96cc84 6972f302 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/09 02:44 upstream 014441d1e4b2 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/07 21:21 upstream 4ae12d8bd9a8 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in restrict_one_thread_callback
2026/03/04 16:22 upstream 0031c06807cf e6b6b96b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/04 05:01 upstream 0031c06807cf 4180d919 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in restrict_one_thread_callback
2026/03/03 20:31 upstream af4e9ef3d784 4180d919 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/02/28 14:31 upstream 4d349ee5c778 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/02/27 23:50 upstream aed968f8a6cd 2cf092b8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/02/27 23:48 upstream aed968f8a6cd 2cf092b8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/02/23 15:27 upstream 6de23f81a5e0 305c0ec5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/02/21 16:15 upstream a95f71ad3e2e 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/03/09 15:58 upstream 1f318b96cc84 176bead5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in restrict_one_thread_callback
2026/03/08 21:54 upstream 014441d1e4b2 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in restrict_one_thread_callback
2026/03/07 10:48 upstream 651690480a96 5cb44a80 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in restrict_one_thread_callback
2026/02/19 13:50 upstream 956b9cbd7f15 746545b8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in restrict_one_thread_callback
2026/02/27 12:19 linux-next 7d6661873f6b a2f13f71 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in restrict_one_thread_callback
2026/02/22 21:26 linux-next d4906ae14a5f 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/02/22 13:20 linux-next d4906ae14a5f 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/02/21 15:12 linux-next d4906ae14a5f 6e7b5511 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/02/19 13:41 linux-next 50f68cc7be0a 746545b8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/02/19 11:44 linux-next 50f68cc7be0a 746545b8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in restrict_one_thread_callback
2026/02/16 06:15 linux-next 635c467cc14e 1e62d198 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-rust-kasan-gce INFO: task hung in restrict_one_thread_callback
* Struck through repros no longer work on HEAD.