syzbot


INFO: task hung in __get_metapage

Status: auto-obsoleted due to no activity on 2023/08/06 10:00
Reported-by: syzbot+934105300cd7257f07c1@syzkaller.appspotmail.com
First crash: 442d, last: 442d
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in __get_metapage (2) jfs C 100 6d03h 109d 0/27 upstream: reported C repro on 2024/03/06 10:57
linux-5.15 INFO: task hung in __get_metapage (2) origin:upstream C 120 34d 78d 0/3 upstream: reported C repro on 2024/04/06 18:07
upstream INFO: task hung in __get_metapage jfs C error done 32 167d 621d 26/27 fixed on 2024/02/21 18:23
linux-6.1 INFO: task hung in __get_metapage 49 42d 73d 0/3 upstream: reported on 2024/04/11 09:44
linux-4.19 INFO: task hung in __get_metapage jfs C error 1 532d 532d 0/1 upstream: reported C repro on 2023/01/08 09:57

Sample crash report:
INFO: task syz-executor.5:30464 blocked for more than 143 seconds.
      Not tainted 5.15.106-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5  state:D stack:    0 pid:30464 ppid:  4088 flags:0x00000009
Call trace:
 __switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0xf10/0x1e38 kernel/sched/core.c:6372
 schedule+0x11c/0x1c8 kernel/sched/core.c:6455
 io_schedule+0x8c/0x194 kernel/sched/core.c:8472
 __lock_metapage+0x1c4/0x438 fs/jfs/jfs_metapage.c:49
 lock_metapage fs/jfs/jfs_metapage.c:63 [inline]
 __get_metapage+0x9b8/0x1128 fs/jfs/jfs_metapage.c:640
 diIAGRead fs/jfs/jfs_imap.c:2662 [inline]
 diNewExt+0x1b98/0x2bbc fs/jfs/jfs_imap.c:2230
 diAllocExt fs/jfs/jfs_imap.c:1945 [inline]
 diAllocAG+0xa68/0x1bbc fs/jfs/jfs_imap.c:1662
 diAlloc+0x360/0x14a4 fs/jfs/jfs_imap.c:1583
 ialloc+0x84/0x7c0 fs/jfs/jfs_inode.c:56
 jfs_mkdir+0x190/0xa0c fs/jfs/namei.c:225
 vfs_mkdir+0x350/0x514 fs/namei.c:3994
 do_mkdirat+0x20c/0x610 fs/namei.c:4019
 __do_sys_mkdirat fs/namei.c:4034 [inline]
 __se_sys_mkdirat fs/namei.c:4032 [inline]
 __arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4032
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor.5:30479 blocked for more than 144 seconds.
      Not tainted 5.15.106-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5  state:D stack:    0 pid:30479 ppid:  4088 flags:0x00000001
Call trace:
 __switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0xf10/0x1e38 kernel/sched/core.c:6372
 schedule+0x11c/0x1c8 kernel/sched/core.c:6455
 rwsem_down_write_slowpath+0xca8/0x1340 kernel/locking/rwsem.c:1157
 __down_write_common kernel/locking/rwsem.c:1284 [inline]
 __down_write kernel/locking/rwsem.c:1293 [inline]
 down_write+0x25c/0x260 kernel/locking/rwsem.c:1542
 inode_lock include/linux/fs.h:787 [inline]
 open_last_lookups fs/namei.c:3459 [inline]
 path_openat+0x63c/0x26f0 fs/namei.c:3669
 do_filp_open+0x1a8/0x3b4 fs/namei.c:3699
 do_sys_openat2+0x128/0x3d8 fs/open.c:1211
 do_sys_open fs/open.c:1227 [inline]
 __do_sys_openat fs/open.c:1243 [inline]
 __se_sys_openat fs/open.c:1238 [inline]
 __arm64_sys_openat+0x1f0/0x240 fs/open.c:1238
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
INFO: task syz-executor.5:30480 blocked for more than 144 seconds.
      Not tainted 5.15.106-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5  state:D stack:    0 pid:30480 ppid:  4088 flags:0x00000009
Call trace:
 __switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
 context_switch kernel/sched/core.c:5026 [inline]
 __schedule+0xf10/0x1e38 kernel/sched/core.c:6372
 schedule+0x11c/0x1c8 kernel/sched/core.c:6455
 io_schedule+0x8c/0x194 kernel/sched/core.c:8472
 __lock_metapage+0x1c4/0x438 fs/jfs/jfs_metapage.c:49
 lock_metapage fs/jfs/jfs_metapage.c:63 [inline]
 __get_metapage+0x9b8/0x1128 fs/jfs/jfs_metapage.c:640
 diIAGRead fs/jfs/jfs_imap.c:2662 [inline]
 diRead+0x1e4/0x94c fs/jfs/jfs_imap.c:315
 jfs_iget+0x88/0x364 fs/jfs/inode.c:35
 jfs_lookup+0x1e8/0x39c fs/jfs/namei.c:1462
 __lookup_slow+0x250/0x388 fs/namei.c:1659
 lookup_slow+0x60/0x84 fs/namei.c:1676
 walk_component+0x394/0x4cc fs/namei.c:1972
 lookup_last fs/namei.c:2427 [inline]
 path_lookupat+0x13c/0x3d0 fs/namei.c:2451
 filename_lookup+0x1c4/0x4c8 fs/namei.c:2480
 user_path_at_empty+0x5c/0x1a4 fs/namei.c:2853
 user_path_at include/linux/namei.h:57 [inline]
 vfs_statx+0xf8/0x378 fs/stat.c:221
 vfs_fstatat fs/stat.c:243 [inline]
 __do_sys_newfstatat fs/stat.c:411 [inline]
 __se_sys_newfstatat fs/stat.c:405 [inline]
 __arm64_sys_newfstatat+0x110/0x194 fs/stat.c:405
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffff800014aa1660 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:268
2 locks held by getty/3735:
 #0: ffff0000d41c0098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x40/0x50 drivers/tty/tty_ldsem.c:340
 #1: ffff80001a28b2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1200 drivers/tty/n_tty.c:2147
2 locks held by kworker/u4:28/22347:
3 locks held by kworker/0:14/27474:
 #0: ffff0000c0020d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x66c/0x11b8 kernel/workqueue.c:2279
 #1: ffff8000262a7c00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x6ac/0x11b8 kernel/workqueue.c:2281
 #2: ffff000142f2b240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x274/0x33c4 drivers/net/netdevsim/fib.c:1478
4 locks held by syz-executor.5/30464:
 #0: ffff000123224460 (sb_writers#24){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
 #1: ffff000127778ec0 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline]
 #1: ffff000127778ec0 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: filename_create+0x200/0x464 fs/namei.c:3765
 #2: ffff0000cedd0920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diAlloc+0x168/0x14a4 fs/jfs/jfs_imap.c:1343
 #3: ffff00012777f038 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diAllocExt fs/jfs/jfs_imap.c:1910 [inline]
 #3: ffff00012777f038 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diAllocAG+0x25c/0x1bbc fs/jfs/jfs_imap.c:1662
2 locks held by syz-executor.5/30479:
 #0: ffff000123224460 (sb_writers#24){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
 #1: ffff000127778ec0 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #1: ffff000127778ec0 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: open_last_lookups fs/namei.c:3459 [inline]
 #1: ffff000127778ec0 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: path_openat+0x63c/0x26f0 fs/namei.c:3669
2 locks held by syz-executor.5/30480:
 #0: ffff00012777a140 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:797 [inline]
 #0: ffff00012777a140 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1675
 #1: ffff00012777f038 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diRead+0x13c/0x94c fs/jfs/jfs_imap.c:314
4 locks held by syz-executor.1/31100:
 #0: ffff000141d56460 (sb_writers#24){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
 #1: ffff00012777bd00 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:822 [inline]
 #1: ffff00012777bd00 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: filename_create+0x200/0x464 fs/namei.c:3765
 #2: ffff0001468f0920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diAlloc+0x168/0x14a4 fs/jfs/jfs_imap.c:1343
 #3: ffff00013fc52638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diAllocExt fs/jfs/jfs_imap.c:1910 [inline]
 #3: ffff00013fc52638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diAllocAG+0x25c/0x1bbc fs/jfs/jfs_imap.c:1662
2 locks held by syz-executor.1/31104:
 #0: ffff000141d56460 (sb_writers#24){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
 #1: ffff00012777bd00 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #1: ffff00012777bd00 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: open_last_lookups fs/namei.c:3459 [inline]
 #1: ffff00012777bd00 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: path_openat+0x63c/0x26f0 fs/namei.c:3669
2 locks held by syz-executor.1/31105:
 #0: ffff00012777c640 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:797 [inline]
 #0: ffff00012777c640 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1675
 #1: ffff00013fc52638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diRead+0x13c/0x94c fs/jfs/jfs_imap.c:314
2 locks held by syz-executor.0/31281:
2 locks held by syz-executor.4/31283:
3 locks held by syz-executor.5/31290:
2 locks held by syz-executor.1/31289:
1 lock held by syz-executor.3/31295:
 #0: ffff0000c7da62d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
 #0: ffff0000c7da62d8 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x15c/0x2b4 mm/util.c:549
1 lock held by syz-executor.3/31296:

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


Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/04/08 10:00 linux-5.15.y d86dfc4d95cd 71147e29 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 INFO: task hung in __get_metapage
* Struck through repros no longer work on HEAD.