syzbot


INFO: task hung in __get_metapage (2)

Status: upstream: reported on 2024/08/05 17:54
Reported-by: syzbot+85d03f851b3b657ad232@syzkaller.appspotmail.com
First crash: 64d, last: 31d
Similar bugs (6)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in __get_metapage (2) jfs C 283 8h38m 217d 0/28 upstream: reported C repro on 2024/03/06 10:57
linux-5.15 INFO: task hung in __get_metapage (2) origin:upstream C 255 5h55m 185d 0/3 upstream: reported C repro on 2024/04/06 18:07
upstream INFO: task hung in __get_metapage jfs C error done 32 275d 729d 25/28 fixed on 2024/02/21 18:23
linux-6.1 INFO: task hung in __get_metapage 49 149d 181d 0/3 auto-obsoleted due to no activity on 2024/07/22 01:46
linux-4.19 INFO: task hung in __get_metapage jfs C error 1 640d 640d 0/1 upstream: reported C repro on 2023/01/08 09:57
linux-5.15 INFO: task hung in __get_metapage 1 550d 550d 0/3 auto-obsoleted due to no activity on 2023/08/06 10:00

Sample crash report:
INFO: task jfsCommit:91 blocked for more than 143 seconds.
      Not tainted 6.1.108-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit       state:D stack:0     pid:91    ppid:2      flags:0x00000008
Call trace:
 __switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0xef4/0x1d44 kernel/sched/core.c:6558
 schedule+0xc4/0x170 kernel/sched/core.c:6634
 io_schedule+0x8c/0x188 kernel/sched/core.c:8786
 __lock_metapage+0x1cc/0x458 fs/jfs/jfs_metapage.c:50
 lock_metapage fs/jfs/jfs_metapage.c:64 [inline]
 __get_metapage+0x96c/0x1050 fs/jfs/jfs_metapage.c:639
 diIAGRead+0xe4/0x14c fs/jfs/jfs_imap.c:2672
 diFree+0x800/0x2648 fs/jfs/jfs_imap.c:959
 jfs_evict_inode+0x2d0/0x3f4 fs/jfs/inode.c:156
 evict+0x418/0x894 fs/inode.c:701
 iput_final fs/inode.c:1826 [inline]
 iput+0x7c0/0x8a4 fs/inode.c:1852
 txUpdateMap+0x73c/0x8e4 fs/jfs/jfs_txnmgr.c:2367
 txLazyCommit fs/jfs/jfs_txnmgr.c:2664 [inline]
 jfs_lazycommit+0x3a0/0x988 fs/jfs/jfs_txnmgr.c:2732
 kthread+0x250/0x2d8 kernel/kthread.c:376
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864

Showing all locks held in the system:
2 locks held by kworker/u4:0/9:
4 locks held by kworker/u4:1/11:
 #0: ffff0000c0845138 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
 #1: ffff80001d137c20 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
 #2: ffff800017fe5850 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0xf4/0x994 net/core/net_namespace.c:566
 #3: ffff800017ff1688 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
1 lock held by rcu_tasks_kthre/12:
 #0: ffff800015ba50b0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
 #0: ffff800015ba58b0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
 #0: ffff800015ba4ee0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
2 locks held by jfsCommit/91:
 #0: ffff0000daf10920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x2cc/0x2648 fs/jfs/jfs_imap.c:889
 #1: ffff0000ec1d2638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x2e0/0x2648 fs/jfs/jfs_imap.c:894
3 locks held by kworker/u4:5/1688:
 #0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
 #1: ffff800025e67c20 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
 #2: ffff800017ff1688 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
2 locks held by getty/4049:
 #0: ffff0000d65c9098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
 #1: ffff80001efd02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2198
3 locks held by kworker/0:4/4347:
 #0: ffff0000d629ad38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
 #1: ffff800021297c20 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
 #2: ffff800017ff1688 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
3 locks held by kworker/1:5/4349:
 #0: ffff0000d629ad38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
 #1: ffff8000213f7c20 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
 #2: ffff800017ff1688 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
3 locks held by kworker/0:10/4453:
 #0: ffff0000c0020938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
 #1: ffff800021577c20 (deferred_process_work){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
 #2: ffff800017ff1688 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74
1 lock held by syz-executor/9400:
 #0: ffff800017ff1688 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
 #0: ffff800017ff1688 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x6e8/0xd94 net/core/rtnetlink.c:6118
1 lock held by syz.0.1667/9640:
 #0: ffff800017ff1688 (rtnl_mutex){+.+.}-{3:3}, at: __netlink_dump_start+0x104/0x680 net/netlink/af_netlink.c:2301
1 lock held by syz.1.1673/9655:
 #0: ffff800017ff1688 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock+0x20/0x2c net/core/rtnetlink.c:74

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


Crashes (8):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/09/07 19:34 linux-6.1.y 699506173494 9750182a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in __get_metapage
2024/08/23 04:51 linux-6.1.y ee5e09825b81 ce8a9099 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in __get_metapage
2024/08/23 04:46 linux-6.1.y ee5e09825b81 ce8a9099 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in __get_metapage
2024/08/14 07:42 linux-6.1.y 36790ef5e00b bde81f6f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in __get_metapage
2024/08/11 10:35 linux-6.1.y 48d525b0e463 6f4edef4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in __get_metapage
2024/08/07 13:28 linux-6.1.y 48d525b0e463 109d2082 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in __get_metapage
2024/08/06 08:27 linux-6.1.y 48d525b0e463 e1bdb00a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in __get_metapage
2024/08/05 17:54 linux-6.1.y 48d525b0e463 e35c337f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in __get_metapage
* Struck through repros no longer work on HEAD.