syzbot


INFO: task hung in release_metapage

Status: upstream: reported C repro on 2024/06/28 06:33
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+132b6f3a657830b63905@syzkaller.appspotmail.com
First crash: 433d, last: 53d
Bug presence (2)
Date Name Commit Repro Result
2024/11/10 linux-5.15.y (ToT) 3c17fc483905 C [report] INFO: task hung in release_metapage
2024/11/10 upstream (ToT) de2f378f2b77 C Didn't crash
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in release_metapage (2) jfs 1 C error 92 13d 35d 0/29 upstream: reported C repro on 2025/07/30 22:55
linux-6.1 INFO: task hung in release_metapage 1 43 381d 429d 0/3 auto-obsoleted due to no activity on 2024/10/28 12:02
upstream INFO: task hung in release_metapage jfs 1 125 392d 439d 0/29 auto-obsoleted due to no activity on 2024/10/17 00:22
Last patch testing requests (4)
Created Duration User Patch Repo Result
2025/08/20 20:44 1h22m retest repro linux-5.15.y OK log
2025/06/10 11:07 23m retest repro linux-5.15.y report log
2025/03/31 18:03 15m retest repro linux-5.15.y report log
2025/01/19 08:04 14m retest repro linux-5.15.y report log
Fix bisection attempts (3)
Created Duration User Patch Repo Result
2025/08/20 16:49 10m fix candidate upstream error job log
2025/06/04 05:08 4m fix candidate upstream error job log
2024/11/16 22:20 1m fix candidate upstream error job log

Sample crash report:
INFO: task syz.5.138:5011 blocked for more than 143 seconds.
      Not tainted 5.15.187-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.5.138       state:D stack:25104 pid: 5011 ppid:  4409 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
 io_schedule+0x7c/0xd0 kernel/sched/core.c:8484
 wait_on_page_bit_common+0x815/0xe00 mm/filemap.c:1356
 lock_page include/linux/pagemap.h:625 [inline]
 release_metapage+0x11f/0xe10 fs/jfs/jfs_metapage.c:736
 discard_metapage fs/jfs/jfs_metapage.h:88 [inline]
 __get_metapage+0xbeb/0x1060 fs/jfs/jfs_metapage.c:645
 dtSearch+0x5d5/0x2050 fs/jfs/jfs_dtree.c:624
 jfs_lookup+0x152/0x380 fs/jfs/namei.c:1459
 __lookup_slow+0x27d/0x3d0 fs/namei.c:1663
 lookup_slow+0x53/0x70 fs/namei.c:1680
 walk_component+0x319/0x460 fs/namei.c:1976
 lookup_last fs/namei.c:2431 [inline]
 path_lookupat+0x169/0x440 fs/namei.c:2455
 filename_lookup+0x1e2/0x4f0 fs/namei.c:2484
 user_path_at_empty+0x40/0x190 fs/namei.c:2883
 user_path_at include/linux/namei.h:57 [inline]
 __do_sys_chdir fs/open.c:490 [inline]
 __se_sys_chdir+0x91/0x280 fs/open.c:484
 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:0x7fe829ed2929
RSP: 002b:00007fe827d3a038 EFLAGS: 00000246 ORIG_RAX: 0000000000000050
RAX: ffffffffffffffda RBX: 00007fe82a0f9fa0 RCX: 00007fe829ed2929
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000a40
RBP: 00007fe829f54b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007fe82a0f9fa0 R15: 00007ffe53708a78
 </TASK>

Showing all locks held in the system:
3 locks held by kworker/0:0/7:
 #0: ffff8880b903a318 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
 #1: ffff8880b9027848 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x4d6/0x810 kernel/sched/psi.c:891
 #2: ffffffff8c120d68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
 #2: ffffffff8c120d68 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845
1 lock held by khungtaskd/27:
 #0: ffffffff8c11c2e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3947:
 #0: ffff88802c3a2098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
5 locks held by kworker/1:14/4620:
 #0: ffff88801b9c2d38 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
 #1: ffffc90003e0fd00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
 #2: ffff888147e8f220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #2: ffff888147e8f220 (&dev->mutex){....}-{3:3}, at: hub_event+0x18f/0x4fa0 drivers/usb/core/hub.c:5781
 #3: ffff88807b3ab220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #3: ffff88807b3ab220 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x460 drivers/base/dd.c:954
 #4: ffff8880514541a8 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
 #4: ffff8880514541a8 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x460 drivers/base/dd.c:954
1 lock held by syz.5.138/5011:
 #0: ffff888072be9800 (&type->i_mutex_dir_key#12){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:797 [inline]
 #0: ffff888072be9800 (&type->i_mutex_dir_key#12){++++}-{3:3}, at: lookup_slow+0x46/0x70 fs/namei.c:1679
2 locks held by syz.1.637/7100:
 #0: ffff88802033a118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xf9/0x7d0 block/bdev.c:915
 #1: ffff8880202ef468 (&lo->lo_mutex){+.+.}-{3:3}, at: lo_release+0x4d/0x1f0 drivers/block/loop.c:2071
2 locks held by syz.4.638/7103:
 #0: ffff88802033e118 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xf9/0x7d0 block/bdev.c:915
 #1: ffff888020488468 (&lo->lo_mutex){+.+.}-{3:3}, at: lo_release+0x4d/0x1f0 drivers/block/loop.c:2071

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.187-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/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 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4962 Comm: kworker/u4:9 Not tainted 5.15.187-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:trace_irq_enable_rcuidle+0x1a/0x180 include/trace/events/preemptirq.h:40
Code: 2b 08 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 55 41 57 41 56 41 54 53 48 89 f3 49 89 fe e8 5d e1 f9 ff 66 90 e8 56 e1 f9 ff <5b> 41 5c 41 5e 41 5f 5d c3 65 44 8b 3d 7d 23 84 7e bf 07 00 00 00
RSP: 0018:ffffc900033bfa60 EFLAGS: 00000093
RAX: ffffffff817df1ca RBX: 0000000000000000 RCX: ffff88802c120000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff814871ba
RBP: ffffc900033bfb38 R08: dffffc0000000000 R09: ffffed100ed97a61
R10: ffffed100ed97a61 R11: 1ffff1100ed97a60 R12: ffffffff897f5eb6
R13: dffffc0000000000 R14: ffffffff814871ba R15: 1ffff92000677f54
FS:  0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c41eb2e CR3: 000000002a70c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 trace_hardirqs_on+0x57/0x80 kernel/trace/trace_preemptirq.c:44
 __local_bh_enable_ip+0x12a/0x1b0 kernel/softirq.c:406
 spin_unlock_bh include/linux/spinlock.h:408 [inline]
 batadv_nc_purge_paths+0x316/0x3b0 net/batman-adv/network-coding.c:475
 batadv_nc_worker+0x327/0x5c0 net/batman-adv/network-coding.c:726
 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 (16):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/13 06:25 linux-5.15.y 2f693b607545 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in release_metapage
2024/11/24 19:01 linux-5.15.y 0a51d2d4527b 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in release_metapage
2024/10/09 03:58 linux-5.15.y 3a5928702e71 402f1df0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in release_metapage
2024/08/02 14:06 linux-5.15.y 7e89efd3ae1c 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in release_metapage
2024/08/01 20:11 linux-5.15.y 7e89efd3ae1c 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in release_metapage
2024/07/01 07:05 linux-5.15.y 4878aadf2d15 757f06b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in release_metapage
2024/06/30 18:12 linux-5.15.y 4878aadf2d15 757f06b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in release_metapage
2024/06/28 18:52 linux-5.15.y 4878aadf2d15 757f06b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in release_metapage
2024/06/28 06:33 linux-5.15.y 4878aadf2d15 6ef39602 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in release_metapage
2025/02/21 17:39 linux-5.15.y c16c81c81336 0808a665 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in release_metapage
2024/11/18 01:12 linux-5.15.y 0a51d2d4527b cfe3a04a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in release_metapage
2024/11/09 09:00 linux-5.15.y 3c17fc483905 6b856513 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 INFO: task hung in release_metapage
2024/11/09 06:12 linux-5.15.y 3c17fc483905 6b856513 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in release_metapage
2024/08/02 13:39 linux-5.15.y 7e89efd3ae1c 1e9c4cf3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in release_metapage
2024/07/02 15:04 linux-5.15.y 4878aadf2d15 07f0a0a0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in release_metapage
2024/06/28 20:46 linux-5.15.y 4878aadf2d15 757f06b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in release_metapage
* Struck through repros no longer work on HEAD.