[v5.15] INFO: task hung in jfs_flush_journal

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1fe619a7d252 Linux 5.15.113
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1071c689280000
kernel config: https://syzkaller.appspot.com/x/.config?x=ab36330fd14820aa
dashboard link: https://syzkaller.appspot.com/bug?extid=c8de65538442b7aa603d
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2d1716ac5a07/disk-1fe619a7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9e9e3ef13603/vmlinux-1fe619a7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/810a025eede3/bzImage-1fe619a7.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c8de65...@syzkaller.appspotmail.com

INFO: task syz-executor.4:3522 blocked for more than 143 seconds.
Not tainted 5.15.113-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:20152 pid: 3522 ppid: 1 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
jfs_flush_journal+0x72b/0xec0 fs/jfs/jfs_logmgr.c:1572
jfs_umount+0xf4/0x370 fs/jfs/jfs_umount.c:58
jfs_put_super+0x86/0x180 fs/jfs/super.c:194
generic_shutdown_super+0x136/0x2c0 fs/super.c:475
kill_block_super+0x7a/0xe0 fs/super.c:1405
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7ff468cb85d7
RSP: 002b:00007fff9e9e1cd8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007ff468cb85d7
RDX: 00007fff9e9e1dab RSI: 000000000000000a RDI: 00007fff9e9e1da0
RBP: 00007fff9e9e1da0 R08: 00000000ffffffff R09: 00007fff9e9e1b70
R10: 00005555558f78b3 R11: 0000000000000246 R12: 00007ff468d11cdc
R13: 00007fff9e9e2e60 R14: 00005555558f7810 R15: 00007fff9e9e2ea0
</TASK>
INFO: task syz-executor.2:22300 blocked for more than 143 seconds.
Not tainted 5.15.113-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.2 state:D stack:25688 pid:22300 ppid: 3530 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5026 [inline]
__schedule+0x12c4/0x4590 kernel/sched/core.c:6372
schedule+0x11b/0x1f0 kernel/sched/core.c:6455
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6514
rwsem_down_read_slowpath+0x605/0xb40 kernel/locking/rwsem.c:1047
__down_read_common kernel/locking/rwsem.c:1231 [inline]
__down_read kernel/locking/rwsem.c:1244 [inline]
down_read+0x9a/0x2e0 kernel/locking/rwsem.c:1490
iterate_supers+0xac/0x1e0 fs/super.c:703
ksys_sync+0xb9/0x1c0 fs/sync.c:102
__do_sys_sync+0xa/0x10 fs/sync.c:113
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fa08e102169
RSP: 002b:00007fa08c674168 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00007fa08e221f80 RCX: 00007fa08e102169
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007fa08e15dca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffde011c3cf R14: 00007fa08c674300 R15: 0000000000022000
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c91c560 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3257:
#0: ffff888023ece098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bb32e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1da0 drivers/tty/n_tty.c:2147
1 lock held by syz-executor.4/3522:
#0: ffff88807de400e0 (&type->s_umount_key#91){++++}-{3:3}, at: deactivate_super+0xa9/0xe0 fs/super.c:365
1 lock held by syz-executor.2/22300:
#0: ffff88807de400e0 (&type->s_umount_key#91){++++}-{3:3}, at: iterate_supers+0xac/0x1e0 fs/super.c:703

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.113-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/16/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 3823 Comm: kworker/u4:15 Not tainted 5.15.113-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/16/2023
Workqueue: bat_events batadv_purge_orig
RIP: 0010:trace_hardirqs_on+0x21/0x80 kernel/trace/trace_preemptirq.c:43
Code: 0f 1f 84 00 00 00 00 00 90 53 e8 1a 8f f9 ff 65 8b 1d 3b d8 7c 7e 31 ff 89 de e8 6a 92 f9 ff 85 db 74 25 65 8b 1d 77 15 7c 7e <89> de 81 e6 00 00 f0 00 31 ff e8 50 92 f9 ff 81 e3 00 00 f0 00 74
RSP: 0018:ffffc900046cfa10 EFLAGS: 00000002
RAX: 0000000000000000 RBX: 0000000080000000 RCX: ffff88801b138000
RDX: ffff88801b138000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc900046cfad0 R08: ffffffff81865a46 R09: ffffed100ababc49
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 1ffff920008d9f4c R14: ffffc900046cfa60 R15: 0000000000000201
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fee21e55788 CR3: 00000000232d3000 CR4: 00000000003506e0
Call Trace:
<TASK>
__local_bh_enable_ip+0x164/0x1f0 kernel/softirq.c:388
spin_unlock_bh include/linux/spinlock.h:408 [inline]
batadv_purge_orig_ref+0x14b9/0x15a0 net/batman-adv/originator.c:1259
batadv_purge_orig+0x15/0x60 net/batman-adv/originator.c:1272
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2307
worker_thread+0xaca/0x1280 kernel/workqueue.c:2454
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.