ci2 starts bisection 2023-06-06 20:20:40.587925774 +0000 UTC m=+430264.234833439
bisecting fixing commit since 1b929c02afd37871d5afb9d498426f83432e71c2
building syzkaller on 44712fbc6b687170984c3562336a415b56d82607
ensuring issue is reproducible on original commit 1b929c02afd37871d5afb9d498426f83432e71c2

testing commit 1b929c02afd37871d5afb9d498426f83432e71c2 gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 3d61f78bdb6196d7b4aadb9751e8aa65c7ab3a9b9b3edf8035db1f71cf7309ba
all runs: crashed: INFO: task hung in __get_metapage
testing current HEAD a4d7d701121981e3c3fe69ade376fe9f26324161
testing commit a4d7d701121981e3c3fe69ade376fe9f26324161 gcc
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
kernel signature: 4c69f24d5293c00238137ea204554028f8584100ea6f6e2f4453754d5c5fd2ec
all runs: crashed: INFO: task hung in __get_metapage
crash still not fixed/happens on the oldest tested release
revisions tested: 2, total time: 40m55.304678134s (build: 28m46.408314858s, test: 11m30.833318314s)
crash still not fixed on HEAD or HEAD had kernel test errors
commit msg: Merge tag 'spi-fix-v6.4-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi
crash: INFO: task hung in __get_metapage
INFO: task jfsCommit:106 blocked for more than 143 seconds.
      Not tainted 6.4.0-rc5-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jfsCommit       state:D stack:26176 pid:106   ppid:2      flags:0x00004000
Call Trace:
 <TASK>
 __schedule+0x1819/0x48a0
 schedule+0xc3/0x180
 io_schedule+0x8c/0x100
 __lock_metapage+0x204/0x310
 __get_metapage+0x3a2/0xcf0
 diIAGRead+0xb2/0x110
 diFree+0x7c1/0x3060
 jfs_evict_inode+0x2b0/0x380
 evict+0x262/0x550
 txUpdateMap+0x64c/0x910
 jfs_lazycommit+0x415/0xa00
 kthread+0x276/0x2f0
 ret_from_fork+0x1f/0x30
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8bf1c010 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8bf1c3d0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20
1 lock held by khungtaskd/28:
 #0: ffffffff8bf1be40 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
5 locks held by kworker/u4:3/46:
2 locks held by jfsCommit/105:
 #0: ffff8880203e8920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x24c/0x3060
 #1: ffff88807497a638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x268/0x3060
2 locks held by jfsCommit/106:
 #0: ffff88802a2c0920 (&(imap->im_aglock[index])){+.+.}-{3:3}, at: diFree+0x24c/0x3060
 #1: ffff888078372638 (&jfs_ip->rdwrlock/1){.+.+}-{3:3}, at: diFree+0x268/0x3060
2 locks held by getty/4737:
 #0: ffff88802b2f2098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x20/0x60
 #1: ffffc900015902f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x3cf/0x11f0
1 lock held by syz-executor.0/5750:
 #0: ffff88806d5a40e0 (&type->s_umount_key#50){+.+.}-{3:3}, at: deactivate_super+0x54/0x80

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.4.0-rc5-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
Call Trace:
 <TASK>
 dump_stack_lvl+0x12e/0x1d0
 nmi_cpu_backtrace+0x2dd/0x310
 nmi_trigger_cpumask_backtrace+0x103/0x1f0
 watchdog+0xa7c/0xac0
 kthread+0x276/0x2f0
 ret_from_fork+0x1f/0x30
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt+0x20/0x30