syzbot


INFO: task hung in __get_metapage

Status: fixed on 2024/02/21 18:23
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+84c274731411665e6c52@syzkaller.appspotmail.com
Fix commit: 6f861765464f fs: Block writes to mounted block devices
First crash: 595d, last: 138d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: fixed by (bisect log) :
commit 6f861765464f43a71462d52026fbddfc858239a5
Author: Jan Kara <jack@suse.cz>
Date: Wed Nov 1 17:43:10 2023 +0000

  fs: Block writes to mounted block devices

  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] INFO: task hung in __get_metapage 1 (3) 2024/02/19 11:56
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 97 9d00h 80d 0/26 upstream: reported C repro on 2024/03/06 10:57
linux-5.15 INFO: task hung in __get_metapage (2) origin:upstream C 120 5d09h 48d 0/3 upstream: reported C repro on 2024/04/06 18:07
linux-6.1 INFO: task hung in __get_metapage 49 12d 44d 0/3 upstream: reported on 2024/04/11 09:44
linux-4.19 INFO: task hung in __get_metapage jfs C error 1 503d 503d 0/1 upstream: reported C repro on 2023/01/08 09:57
linux-5.15 INFO: task hung in __get_metapage 1 413d 413d 0/3 auto-obsoleted due to no activity on 2023/08/06 10:00
Last patch testing requests (10)
Created Duration User Patch Repo Result
2024/02/17 17:52 23m retest repro upstream OK log
2024/02/02 12:14 31m retest repro upstream OK log
2024/01/22 07:24 18m retest repro upstream OK log
2024/01/22 07:24 19m retest repro upstream OK log
2023/12/25 01:19 13m retest repro upstream report log
2023/11/23 23:36 16m retest repro upstream report log
2023/11/01 10:32 16m retest repro upstream report log
2023/11/01 09:37 13m retest repro upstream report log
2023/10/07 00:52 16m retest repro upstream report log
2023/09/07 03:12 17m retest repro upstream report log
Fix bisection attempts (7)
Created Duration User Patch Repo Result
2024/02/19 00:06 5h18m bisect fix upstream job log (1)
2024/01/08 05:22 1h27m bisect fix upstream job log (0) log
2023/12/09 01:54 3h27m bisect fix upstream job log (0) log
2023/10/15 23:17 1h55m bisect fix upstream job log (0) log
2023/07/25 14:25 1h46m (2) bisect fix upstream job log (0) log
2023/06/06 20:20 41m bisect fix upstream job log (0) log
2023/02/11 03:23 59m bisect fix upstream job log (0) log

Sample crash report:
INFO: task jfsCommit:107 blocked for more than 143 seconds.
      Not tainted 6.4.0-rc7-syzkaller-00014-g692b7dc87ca6 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit       state:D stack:26112 pid:107   ppid:2      flags:0x00004000
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0x187b/0x4900 kernel/sched/core.c:6669
 schedule+0xc3/0x180 kernel/sched/core.c:6745
 io_schedule+0x8c/0x100 kernel/sched/core.c:8979
 __lock_metapage+0x1f9/0x310 fs/jfs/jfs_metapage.c:50
 lock_metapage fs/jfs/jfs_metapage.c:64 [inline]
 __get_metapage+0x556/0x10e0 fs/jfs/jfs_metapage.c:639
 diIAGRead+0xcb/0x130 fs/jfs/jfs_imap.c:2662
 diFree+0xa7e/0x2fb0 fs/jfs/jfs_imap.c:955
 jfs_evict_inode+0x32d/0x440 fs/jfs/inode.c:156
 evict+0x2a4/0x620 fs/inode.c:665
 txUpdateMap+0x829/0x9e0 fs/jfs/jfs_txnmgr.c:2362
 txLazyCommit fs/jfs/jfs_txnmgr.c:2659 [inline]
 jfs_lazycommit+0x47a/0xb70 fs/jfs/jfs_txnmgr.c:2727
 kthread+0x2b8/0x350 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8cf276f0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:518
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8cf27ab0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:518
1 lock held by khungtaskd/28:
 #0: ffffffff8cf27520 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by jfsCommit/107:
 #0: ffff88802b930920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x37c/0x2fb0 fs/jfs/jfs_imap.c:885
 #1: ffff888074a62638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x398/0x2fb0 fs/jfs/jfs_imap.c:890
2 locks held by getty/4758:
 #0: ffff88802933b098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900015802f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6ab/0x1db0 drivers/tty/n_tty.c:2176
2 locks held by syz-executor357/5827:

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

NMI backtrace for cpu 1
CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.4.0-rc7-syzkaller-00014-g692b7dc87ca6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x498/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x187/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xec2/0xf00 kernel/hung_task.c:379
 kthread+0x2b8/0x350 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 5827 Comm: syz-executor357 Not tainted 6.4.0-rc7-syzkaller-00014-g692b7dc87ca6 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023
RIP: 0010:get_current arch/x86/include/asm/current.h:41 [inline]
RIP: 0010:write_comp_data kernel/kcov.c:235 [inline]
RIP: 0010:__sanitizer_cov_trace_const_cmp1+0x8/0x90 kernel/kcov.c:290
Code: 49 ff c2 4c 89 12 48 c7 44 11 08 06 00 00 00 48 89 7c 11 10 48 89 74 11 18 4c 89 44 11 20 c3 0f 1f 00 f3 0f 1e fa 4c 8b 04 24 <65> 48 8b 15 80 35 78 7e 65 8b 05 81 35 78 7e a9 00 01 ff 00 74 10
RSP: 0018:ffffc90003f4f4d8 EFLAGS: 00000046
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff88806fa3bb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000040
RBP: dffffc0000000000 R08: ffffffff8aabd636 R09: fffff94000389c99
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88806cdf8580
R13: 0000000000000249 R14: ffffc90003f4f680 R15: ffff88806cdf8580
FS:  0000555556f50300(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f569724c000 CR3: 0000000022b60000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 get_offset lib/xarray.c:146 [inline]
 xas_descend+0x66/0x440 lib/xarray.c:205
 xas_load lib/xarray.c:244 [inline]
 xas_store+0x19b/0x1960 lib/xarray.c:789
 page_cache_delete mm/filemap.c:142 [inline]
 __filemap_remove_folio+0x695/0xad0 mm/filemap.c:225
 filemap_remove_folio+0x109/0x2e0 mm/filemap.c:257
 truncate_inode_folio+0x5d/0x70 mm/truncate.c:196
 shmem_undo_range+0x43d/0x1ba0 mm/shmem.c:950
 shmem_truncate_range mm/shmem.c:1049 [inline]
 shmem_evict_inode+0x258/0x9f0 mm/shmem.c:1164
 evict+0x2a4/0x620 fs/inode.c:665
 __dentry_kill+0x436/0x650 fs/dcache.c:607
 dentry_kill+0xbb/0x290
 dput+0x1f3/0x420 fs/dcache.c:913
 __fput+0x5e4/0x890 fs/file_table.c:329
 task_work_run+0x24a/0x300 kernel/task_work.c:179
 ptrace_notify+0x2cd/0x380 kernel/signal.c:2371
 ptrace_report_syscall include/linux/ptrace.h:411 [inline]
 ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]
 syscall_exit_work kernel/entry/common.c:252 [inline]
 syscall_exit_to_user_mode_prepare kernel/entry/common.c:279 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:284 [inline]
 syscall_exit_to_user_mode+0x157/0x280 kernel/entry/common.c:297
 do_syscall_64+0x4d/0xc0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f569e6581a3
Code: c7 c2 c0 ff ff ff f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb ba 0f 1f 00 64 8b 04 25 18 00 00 00 85 c0 75 14 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8
RSP: 002b:00007ffcae469658 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000003 RCX: 00007f569e6581a3
RDX: 0000000000000010 RSI: 0000000000004c00 RDI: 0000000000000003
RBP: 00007ffcae469670 R08: 0000000000005ea8 R09: 0000000000005ea4
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000004
R13: 0000555556f502c0 R14: 000000000020c082 R15: 00007ffcae4696b0
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.438 msecs

Crashes (32):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/06/20 14:10 upstream 692b7dc87ca6 09ffe269 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root INFO: task hung in __get_metapage
2023/06/07 05:48 upstream a4d7d7011219 a4ae4f42 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root INFO: task hung in __get_metapage
2022/12/28 13:25 upstream 1b929c02afd3 44712fbc .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __get_metapage
2022/12/19 04:34 upstream f9ff5644bcc0 05494336 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in __get_metapage
2022/10/11 09:12 upstream 493ffd6605b2 5bcf0c31 .config strace log report syz C [disk image] [vmlinux] [mounted in repro] ci2-upstream-fs INFO: task hung in __get_metapage
2023/05/07 18:55 upstream fc4354c6e5c2 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2023/04/07 08:17 upstream f2afccfefe7b 00ce4c67 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2023/04/03 21:43 upstream 148341f0a2f5 41147e3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2023/04/02 17:36 upstream 00c7b5f4ddc5 f325deb0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2023/03/27 03:31 upstream 18940c888c85 fbf0499a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2023/03/17 23:20 upstream 38e04b3e4240 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2023/01/12 03:22 upstream 7dd4b804e080 96166539 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2023/01/12 01:53 upstream 7dd4b804e080 96166539 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2022/12/30 15:43 upstream 2258c2dc850b 44712fbc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2022/12/27 17:48 upstream 1b929c02afd3 44712fbc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2022/12/25 20:28 upstream 72a85e2b0a1e 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2022/12/20 15:26 upstream aeba12b26c79 c52b2efb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2022/12/18 20:26 upstream f9ff5644bcc0 05494336 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2022/12/04 04:11 upstream c2bf05db6c78 e080de16 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2022/11/02 14:56 upstream b229b6ca5abb 08977f5d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in __get_metapage
2022/10/24 11:40 upstream 247f34f7b803 faae2fda .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in __get_metapage
2022/10/20 04:19 upstream 55be6084c8e0 b31320fc .config console log report info [disk image] [vmlinux] ci-upstream-kasan-gce-smack-root INFO: task hung in __get_metapage
2022/10/15 05:07 upstream 493ffd6605b2 67cb024c .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in __get_metapage
2022/10/15 00:26 upstream 493ffd6605b2 67cb024c .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in __get_metapage
2022/10/14 11:20 upstream 493ffd6605b2 4954e4b2 .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in __get_metapage
2022/10/08 17:36 upstream 62e6e5940c0c aea5da89 .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in __get_metapage
2023/11/09 01:46 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c df3908d6 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in __get_metapage
2023/06/11 11:15 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d8b213732169 7086cdb9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in __get_metapage
2023/04/25 10:04 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 14f8db1c0f9a fdc18293 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in __get_metapage
2023/04/04 03:51 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 59caa87f9dfb 7db618d0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in __get_metapage
2023/03/07 08:44 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci fe15c26ee26e f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in __get_metapage
2022/12/14 01:07 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a5541c0811a0 e660de91 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in __get_metapage
* Struck through repros no longer work on HEAD.