syzbot


INFO: task hung in lock_metapage

Status: upstream: reported C repro on 2022/10/26 22:58
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+1d84a1682e4673d5c4fb@syzkaller.appspotmail.com
First crash: 1140d, last: 2h01m
Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: INFO: task hung in lock_metapage (log)
Repro: C syz .config
  
Fix bisection: failed (error log, bisect log)
  
Discussions (20)
Title Replies (including bot) Last reply
[syzbot] Monthly jfs report (Nov 2025) 0 (1) 2025/11/25 08:46
[syzbot] Monthly jfs report (Oct 2025) 0 (1) 2025/10/24 18:48
[syzbot] Monthly jfs report (Sep 2025) 0 (1) 2025/09/23 06:49
[syzbot] Monthly jfs report (Aug 2025) 0 (1) 2025/08/23 16:31
[syzbot] Monthly jfs report (Jul 2025) 0 (1) 2025/07/22 12:43
[syzbot] Monthly jfs report (Jun 2025) 0 (1) 2025/06/23 07:31
[syzbot] Monthly jfs report (May 2025) 0 (1) 2025/05/21 14:56
[syzbot] Monthly jfs report (Apr 2025) 0 (1) 2025/04/22 10:11
[syzbot] Monthly jfs report (Mar 2025) 0 (1) 2025/03/19 21:29
[syzbot] Monthly jfs report (Feb 2025) 0 (1) 2025/02/16 21:54
[syzbot] Monthly jfs report (Jan 2025) 0 (1) 2025/01/16 10:11
[syzbot] Monthly jfs report (Dec 2024) 0 (1) 2024/12/16 09:45
[syzbot] Monthly jfs report (Nov 2024) 0 (1) 2024/11/15 10:49
[syzbot] Monthly jfs report (Oct 2024) 0 (1) 2024/10/14 19:37
[syzbot] Monthly jfs report (Sep 2024) 0 (1) 2024/09/13 10:03
[syzbot] Monthly jfs report (Aug 2024) 0 (1) 2024/08/13 08:52
[syzbot] Monthly jfs report (Jul 2024) 0 (1) 2024/07/12 12:56
[syzbot] Monthly jfs report (Jun 2024) 0 (1) 2024/06/11 08:27
[syzbot] Monthly jfs report (May 2024) 0 (1) 2024/05/08 14:26
[syzbot] INFO: task hung in lock_metapage 0 (1) 2022/10/26 22:58
Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.6 INFO: task hung in lock_metapage origin:upstream 1 C 22 4d14h 139d 0/2 upstream: reported C repro on 2025/07/20 10:34
linux-6.1 INFO: task hung in lock_metapage origin:upstream 1 C error 254 1d12h 602d 0/3 upstream: reported C repro on 2024/04/13 05:49
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/03/04 23:44 15m retest repro upstream report log
2024/01/27 11:16 22m retest repro upstream OK log
2024/01/25 08:03 23m retest repro upstream OK log
2023/12/23 12:54 18m retest repro upstream report log
2023/11/15 04:17 2h53m retest repro upstream report log
2023/11/15 04:17 33m retest repro upstream report log
2023/11/15 00:40 40m retest repro linux-next OK log
2023/11/15 00:40 23m retest repro linux-next OK log
2023/11/15 00:40 23m retest repro linux-next OK log
2023/09/26 03:39 17m retest repro upstream report log
Fix bisection attempts (6)
Created Duration User Patch Repo Result
2024/02/01 15:58 12h04m bisect fix upstream error job log
2023/07/18 00:12 1h40m bisect fix upstream OK (0) job log log
2023/06/04 10:17 31m bisect fix upstream OK (0) job log log
2023/05/04 22:11 29m bisect fix upstream OK (0) job log log
2023/04/04 21:39 31m bisect fix upstream OK (0) job log log
2023/01/27 14:55 31m bisect fix upstream OK (0) job log log

Sample crash report:
INFO: task jfsCommit:123 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit       state:D stack:26640 pid:123   tgid:123   ppid:2      task_flags:0x200040 flags:0x00080000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5248 [inline]
 __schedule+0x1480/0x50a0 kernel/sched/core.c:6855
 __schedule_loop kernel/sched/core.c:6937 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6952
 io_schedule+0x81/0xe0 kernel/sched/core.c:7784
 __lock_metapage fs/jfs/jfs_metapage.c:52 [inline]
 lock_metapage+0x1f3/0x400 fs/jfs/jfs_metapage.c:66
 __get_metapage+0x497/0xde0 fs/jfs/jfs_metapage.c:748
 diIAGRead+0xce/0x140 fs/jfs/jfs_imap.c:2672
 diFree+0x97f/0x2c30 fs/jfs/jfs_imap.c:959
 jfs_evict_inode+0x331/0x440 fs/jfs/inode.c:162
 evict+0x5f4/0xae0 fs/inode.c:837
 txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline]
 jfs_lazycommit+0x3f1/0xa10 fs/jfs/jfs_txnmgr.c:2734
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x599/0xb30 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/38:
 #0: ffffffff8d5ae9e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8d5ae9e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:867 [inline]
 #0: ffffffff8d5ae9e0 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6775
3 locks held by kworker/1:1/44:
 #0: ffff88813ff55138 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3238 [inline]
 #0: ffff88813ff55138 ((wq_completion)events){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x1770 kernel/workqueue.c:3346
 #1: ffffc90000b57b80 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3239 [inline]
 #1: ffffc90000b57b80 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x1770 kernel/workqueue.c:3346
 #2: ffff88803738d260 (&data->fib_lock){+.+.}-{4:4}, at: nsim_fib_event_work+0x224/0x3e0 drivers/net/netdevsim/fib.c:1490
3 locks held by kworker/u8:3/45:
 #0: ffff88802f80e138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3238 [inline]
 #0: ffff88802f80e138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x9b4/0x1770 kernel/workqueue.c:3346
 #1: ffffc90000b77b80 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:3239 [inline]
 #1: ffffc90000b77b80 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x9ef/0x1770 kernel/workqueue.c:3346
 #2: ffffffff8e888a78 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_net_lock include/linux/rtnetlink.h:130 [inline]
 #2: ffffffff8e888a78 (rtnl_mutex){+.+.}-{4:4}, at: addrconf_dad_work+0x119/0x15a0 net/ipv6/addrconf.c:4194
2 locks held by jfsCommit/122:
 #0: ffff88803b1e8900 (&(imap->im_aglock[index])){+.+.}-{4:4}, at: diFree+0x29b/0x2c30 fs/jfs/jfs_imap.c:889
 #1: ffff88805b25eca8 (&jfs_ip->rdwrlock/1){.+.+}-{4:4}, at: diFree+0x2b9/0x2c30 fs/jfs/jfs_imap.c:894
2 locks held by jfsCommit/123:
 #0: ffff888056490900 (&(imap->im_aglock[index])){+.+.}-{4:4}, at: diFree+0x29b/0x2c30 fs/jfs/jfs_imap.c:889
 #1: ffff88805b25a868 (&jfs_ip->rdwrlock/1){.+.+}-{4:4}, at: diFree+0x2b9/0x2c30 fs/jfs/jfs_imap.c:894
3 locks held by kworker/u8:15/4280:
1 lock held by udevd/5172:
2 locks held by getty/5561:
 #0: ffff88823bf988a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90003e762e0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x444/0x1400 drivers/tty/n_tty.c:2222
7 locks held by kworker/1:3/5924:
2 locks held by kworker/1:4/5935:
1 lock held by syz-executor/5941:
 #0: ffff8880307fe0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff8880307fe0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff8880307fe0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
2 locks held by syz-executor/5944:
 #0: ffff8881433aa0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff8881433aa0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff8881433aa0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
 #1: ffffffff8d9ed718 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
1 lock held by syz-executor/5951:
 #0: ffff888026b540d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888026b540d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888026b540d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
2 locks held by syz-executor/5952:
 #0: ffff888040e600d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888040e600d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888040e600d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
 #1: ffffffff8d9ed718 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
2 locks held by syz-executor/6181:
 #0: ffff888057f5e0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888057f5e0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888057f5e0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
 #1: ffffffff8d9ed718 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
2 locks held by syz-executor/6223:
 #0: ffff88802467a0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff88802467a0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff88802467a0d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
 #1: ffffffff8d9ed718 (jfs_log_mutex){+.+.}-{4:4}, at: lmLogClose+0xb4/0x520 fs/jfs/jfs_logmgr.c:1443
4 locks held by syz-executor/6224:
 #0: ffff888058d82480 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:499
 #1: ffff88805b25d3b8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1072 [inline]
 #1: ffff88805b25d3b8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2864 [inline]
 #1: ffff88805b25d3b8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2875 [inline]
 #1: ffff88805b25d3b8 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: do_unlinkat+0x1b2/0x570 fs/namei.c:5420
 #2: ffff88805b25f0f8 (&sb->s_type->i_mutex_key#22){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1027 [inline]
 #2: ffff88805b25f0f8 (&sb->s_type->i_mutex_key#22){+.+.}-{4:4}, at: vfs_unlink+0xef/0x650 fs/namei.c:5355
 #3: ffff88805b25eca8 (&jfs_ip->rdwrlock#2){+.+.}-{4:4}, at: jfs_unlink+0x1d8/0xa20 fs/jfs/namei.c:488
1 lock held by syz-executor/6241:
 #0: ffff8880369980d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff8880369980d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff8880369980d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
1 lock held by syz-executor/6259:
 #0: ffff8880406b80d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff8880406b80d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff8880406b80d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
3 locks held by kworker/0:6/6406:
1 lock held by syz-executor/6563:
 #0: ffff888035cb60d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock fs/super.c:57 [inline]
 #0: ffff888035cb60d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: __super_lock_excl fs/super.c:72 [inline]
 #0: ffff888035cb60d0 (&type->s_umount_key#54){+.+.}-{4:4}, at: deactivate_super+0xa9/0xe0 fs/super.c:506
7 locks held by syz-executor/6749:
 #0: ffff8880341ee480 (sb_writers#7){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2682 [inline]
 #0: ffff8880341ee480 (sb_writers#7){.+.+}-{0:0}, at: vfs_write+0x217/0xb40 fs/read_write.c:682
 #1: ffff88803d6ecc78 (&of->mutex){+.+.}-{4:4}, at: kernfs_fop_write_iter+0x1df/0x540 fs/kernfs/file.c:343
 #2: ffff8880271a83c8 (kn->active#57){.+.+}-{0:0}, at: kernfs_get_active_of fs/kernfs/file.c:80 [inline]
 #2: ffff8880271a83c8 (kn->active#57){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x232/0x540 fs/kernfs/file.c:344
 #3: ffffffff8e1120f8 (nsim_bus_dev_list_lock){+.+.}-{4:4}, at: del_device_store+0xd1/0x360 drivers/net/netdevsim/bus.c:234
 #4: ffff888023af20d8 (&dev->mutex){....}-{4:4}, at: device_lock include/linux/device.h:914 [inline]
 #4: ffff888023af20d8 (&dev->mutex){....}-{4:4}, at: __device_driver_lock drivers/base/dd.c:1096 [inline]
 #4: ffff888023af20d8 (&dev->mutex){....}-{4:4}, at: device_release_driver_internal+0xb6/0x800 drivers/base/dd.c:1294
 #5: ffff888023af1300 (&devlink->lock_key#7){+.+.}-{4:4}, at: nsim_drv_remove+0x50/0x160 drivers/net/netdevsim/dev.c:1721
 #6: ffffffff8e888a78 (rtnl_mutex){+.+.}-{4:4}, at: nsim_destroy+0xed/0x680 drivers/net/netdevsim/netdev.c:1173
1 lock held by syz.3.75/6796:
1 lock held by syz.1.76/6798:
3 locks held by syz.0.78/6801:
2 locks held by udevd/6808:
 #0: ffff888034ba0480 (sb_writers#5){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:499
 #1: ffff8880b8833bd0 ((lock)#2){+.+.}-{3:3}, at: spin_lock include/linux/spinlock_rt.h:44 [inline]
 #1: ffff8880b8833bd0 ((lock)#2){+.+.}-{3:3}, at: lru_add_drain+0x137/0x3f0 mm/swap.c:736
5 locks held by dhcpcd-run-hook/6811:
 #0: ffff888026716bc8 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x1a7/0x4a0 mm/mmap_lock.c:238
 #1: ffffffff8d5ae9e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #1: ffffffff8d5ae9e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:867 [inline]
 #1: ffffffff8d5ae9e0 (rcu_read_lock){....}-{1:3}, at: ___pte_offset_map+0x29/0x200 mm/pgtable-generic.c:286
 #2: ffff8880381b0958 (ptlock_ptr(ptdesc)#2){+.+.}-{3:3}, at: spin_lock include/linux/spinlock_rt.h:44 [inline]
 #2: ffff8880381b0958 (ptlock_ptr(ptdesc)#2){+.+.}-{3:3}, at: __pte_offset_map_lock+0x13e/0x210 mm/pgtable-generic.c:401
 #3: ffffffff8d5ae9e0 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #3: ffffffff8d5ae9e0 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:867 [inline]
 #3: ffffffff8d5ae9e0 (rcu_read_lock){....}-{1:3}, at: __rt_spin_lock kernel/locking/spinlock_rt.c:50 [inline]
 #3: ffffffff8d5ae9e0 (rcu_read_lock){....}-{1:3}, at: rt_spin_lock+0x1c1/0x3e0 kernel/locking/spinlock_rt.c:57
 #4: ffff8880b8833bd0 ((lock)#2){+.+.}-{3:3}, at: spin_lock include/linux/spinlock_rt.h:44 [inline]
 #4: ffff8880b8833bd0 ((lock)#2){+.+.}-{3:3}, at: __folio_batch_add_and_move+0x284/0xa90 mm/swap.c:-1

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 38 Comm: khungtaskd Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:332 [inline]
 watchdog+0xf3c/0xf80 kernel/hung_task.c:495
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x599/0xb30 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 1452 Comm: kworker/u8:11 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: kvfree_rcu_reclaim kfree_rcu_work
RIP: 0010:mark_held_locks kernel/locking/lockdep.c:4313 [inline]
RIP: 0010:__trace_hardirqs_on_caller kernel/locking/lockdep.c:4343 [inline]
RIP: 0010:lockdep_hardirqs_on_prepare+0xf3/0x290 kernel/locking/lockdep.c:4410
Code: 10 83 bb 58 0b 00 00 00 0f 8e d1 00 00 00 49 89 de 49 81 c6 60 0b 00 00 45 31 ff 4d 89 f4 eb 13 49 ff c7 48 63 83 58 0b 00 00 <49> 83 c4 28 49 39 c7 7d 44 49 83 ff 31 73 2d 41 8b 44 24 20 a9 00
RSP: 0018:ffffc900057cf8a0 EFLAGS: 00000002
RAX: 0000000000000002 RBX: ffff888027765a00 RCX: ffffffff92555518
RDX: 0000000000000002 RSI: ffff888027766560 RDI: ffff888027765a00
RBP: ffffc900057cf970 R08: ffffffff8ed94f77 R09: 1ffffffff1db29ee
R10: dffffc0000000000 R11: fffffbfff1db29ef R12: ffff888027766560
R13: ffffc900057cf9e0 R14: ffff888027766560 R15: 0000000000000001
FS:  0000000000000000(0000) GS:ffff888126e85000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffedd576e54 CR3: 0000000037012000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 trace_hardirqs_on+0x28/0x40 kernel/trace/trace_preemptirq.c:78
 __raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:151 [inline]
 _raw_spin_unlock_irqrestore+0x85/0x110 kernel/locking/spinlock.c:194
 debug_rcu_head_unqueue kernel/rcu/rcu.h:248 [inline]
 debug_rcu_bhead_unqueue mm/slab_common.c:1438 [inline]
 kvfree_rcu_bulk+0x5a/0x1f0 mm/slab_common.c:1515
 kfree_rcu_work+0xed/0x170 mm/slab_common.c:1600
 process_one_work kernel/workqueue.c:3263 [inline]
 process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3346
 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x599/0xb30 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </TASK>

Crashes (3857):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/03 09:24 upstream d61f1cc5db79 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in lock_metapage
2025/12/01 11:49 upstream 7d0a66e4bb90 d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in lock_metapage
2025/10/07 14:08 upstream c746c3b51698 8ef35d49 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/08/03 10:48 upstream 186f3edfdd41 7368264b .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/07/20 20:05 upstream f4a40a4282f4 7117feec .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in lock_metapage
2025/07/19 03:41 upstream d786aba32000 f550e092 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/01/03 12:13 upstream 0bc21e701a6f d3ccff63 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in lock_metapage
2024/09/06 10:23 upstream ad618736883b 464ac2ed .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in lock_metapage
2024/04/26 04:43 upstream e33c4963bf53 8bdc0f22 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in lock_metapage
2024/04/08 03:55 upstream fe46a7dd189e ca620dd8 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in lock_metapage
2024/02/19 23:23 upstream b401b621758e 3af7dd65 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in lock_metapage
2023/02/12 19:57 upstream f339c2597ebb 93e26d60 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/15 15:57 upstream 7a0892d2836e f7988ea4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root INFO: task hung in lock_metapage
2025/11/15 12:19 upstream 7a0892d2836e f7988ea4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root INFO: task hung in lock_metapage
2025/11/15 08:48 upstream 7a0892d2836e f7988ea4 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root INFO: task hung in lock_metapage
2025/09/22 01:54 upstream f975f08c2e89 67c37560 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root INFO: task hung in lock_metapage
2025/06/11 08:44 upstream aef17cb3d3c4 5d7e17ca .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root INFO: task hung in lock_metapage
2024/12/09 15:29 linux-next af2ea8ab7a54 9ac0fdc6 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2023/07/28 09:12 upstream 57012c57536f 92476829 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-selinux-root INFO: task hung in lock_metapage
2022/10/22 22:51 upstream 4da34b7d175d c0b80a55 .config strace log report syz C [disk image] [vmlinux] [mounted in repro] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2023/03/05 21:39 linux-next 1acf39ef8f14 f8902b57 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2023/02/13 06:11 linux-next 38d2b86a665b 93e26d60 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2022/11/20 15:27 linux-next 15f3bff12cf6 5bb70014 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/12/06 08:37 upstream 7203ca412fc8 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/06 05:22 upstream d1d36025a617 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/12/06 00:46 upstream 7203ca412fc8 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/05 21:18 upstream 2061f18ad76e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/05 11:08 upstream 2061f18ad76e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/04 21:42 upstream 2aa680df6806 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/04 09:29 upstream 559e608c4655 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/03 17:57 upstream 3f9f0252130e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/03 17:57 upstream 3f9f0252130e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/03 05:33 upstream 619f4edc8d4f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/02 23:30 upstream 4a26e7032d7d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/12/02 15:02 upstream 4a26e7032d7d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/02 10:18 upstream 1d18101a644e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/12/02 02:18 upstream 1d18101a644e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/12/01 09:17 upstream 7d0a66e4bb90 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/30 20:52 upstream e69c7c175115 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/30 19:39 upstream e69c7c175115 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/30 15:42 upstream 6bda50f4333f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/30 14:32 upstream 6bda50f4333f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/30 12:38 upstream 6bda50f4333f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/30 11:36 upstream 6bda50f4333f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/30 07:46 upstream 6bda50f4333f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/30 05:55 upstream 6bda50f4333f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/30 04:27 upstream 6bda50f4333f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/30 04:23 upstream 6bda50f4333f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/30 02:19 upstream 6bda50f4333f d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/29 15:16 upstream 19eef1d98eed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/29 10:15 upstream 19eef1d98eed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/28 20:44 upstream e538109ac71d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/28 10:51 upstream e1afacb68573 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/27 18:19 upstream 765e56e41a5a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_metapage
2025/11/26 21:31 upstream 30f09200cc4a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/26 01:25 upstream 8a2bcda5e139 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/25 18:40 upstream 8a2bcda5e139 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/25 12:58 upstream ac3fd01e4c1e 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/24 19:15 upstream ac3fd01e4c1e bf6fe8fe .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/23 06:00 upstream 89edd36fd801 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/22 14:01 upstream 2eba5e05d9bc 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/20 15:43 upstream 23cb64fb7625 2cc4c24a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/20 07:47 upstream 23cb64fb7625 26ee5237 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/20 00:25 upstream 23cb64fb7625 26ee5237 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/19 22:27 upstream 23cb64fb7625 26ee5237 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2025/11/19 14:30 upstream 8b690556d8fe 26ee5237 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_metapage
2024/06/26 05:49 upstream 55027e689933 dec8bc94 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in lock_metapage
2024/06/16 23:12 upstream 2ccbdf43d5e7 f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in lock_metapage
2025/12/05 07:15 linux-next 6987d58a9cbc d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/12/02 00:21 linux-next 7d31f578f323 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/12/01 06:31 linux-next 7d31f578f323 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/11/30 08:57 linux-next 7d31f578f323 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/11/28 04:17 linux-next ef68bf704646 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/11/24 11:48 linux-next d724c6f85e80 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/11/23 23:29 linux-next d724c6f85e80 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
2025/11/23 19:54 linux-next d724c6f85e80 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_metapage
* Struck through repros no longer work on HEAD.