[v6.1] INFO: task hung in jbd2_journal_commit_transaction

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d2869ace6eeb Linux 6.1.31
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11728ced280000
kernel config: https://syzkaller.appspot.com/x/.config?x=623aacf949348d7d
dashboard link: https://syzkaller.appspot.com/bug?extid=f3d88f385bebd43fd9c7
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/2ed651ed0d8f/disk-d2869ace.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b8d3199c542c/vmlinux-d2869ace.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a44812549bf7/bzImage-d2869ace.xz

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

INFO: task jbd2/sda1-8:2963 blocked for more than 143 seconds.
Not tainted 6.1.31-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:jbd2/sda1-8 state:D stack:22808 pid:2963 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5241 [inline]
__schedule+0x132c/0x4330 kernel/sched/core.c:6554
schedule+0xbf/0x180 kernel/sched/core.c:6630
jbd2_journal_wait_updates+0x1f8/0x2d0 fs/jbd2/transaction.c:862
jbd2_journal_commit_transaction+0xb5f/0x6b30 fs/jbd2/commit.c:488
kjournald2+0x45e/0x840 fs/jbd2/journal.c:210
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cf27470 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cf27c70 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x29/0xd20 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
#0: ffffffff8cf272a0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3301:
#0: ffff88823bcd6898 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc900031262f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6a7/0x1db0 drivers/tty/n_tty.c:2177
4 locks held by syz-executor.1/13656:
3 locks held by kworker/u4:11/18329:

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

NMI backtrace for cpu 0
CPU: 0 PID: 28 Comm: khungtaskd Not tainted 6.1.31-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/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+0x4e1/0x560 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1b0/0x3f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xf18/0xf60 kernel/hung_task.c:377
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 13656 Comm: syz-executor.1 Not tainted 6.1.31-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:vmpressure+0x94/0x2c0 mm/vmpressure.c:276
Code: 00 00 49 be 00 00 00 00 00 fc ff df 49 8d 6c 24 20 48 89 ef e8 cd 15 a4 08 49 8d 7c 24 10 48 89 f8 48 c1 e8 03 42 80 3c 30 00 <74> 05 e8 c5 83 f7 ff 4c 03 7b 10 4c 89 7b 10 49 8d 5c 24 18 48 89
RSP: 0018:ffffc900032aecc8 EFLAGS: 00000246
RAX: 1ffff1100f5b8095 RBX: ffff88807adc0498 RCX: 0000000000000001
RDX: dffffc0000000000 RSI: 0000000000000004 RDI: ffff88807adc04a8
RBP: ffff88807adc04b8 R08: dffffc0000000000 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: ffff88807adc0498
R13: 0000000000000001 R14: dffffc0000000000 R15: 0000000000000040
FS: 0000555556995400(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c011367608 CR3: 000000003d591000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
shrink_node+0xcd6/0x2940 mm/vmscan.c:6167
shrink_zones mm/vmscan.c:6396 [inline]
do_try_to_free_pages+0x751/0x1a50 mm/vmscan.c:6458
try_to_free_mem_cgroup_pages+0x46f/0xb70 mm/vmscan.c:6773
try_charge_memcg+0x5d6/0x16b0 mm/memcontrol.c:2681
try_charge mm/memcontrol.c:2823 [inline]
charge_memcg+0x116/0x3f0 mm/memcontrol.c:6894
__mem_cgroup_charge+0x23/0x80 mm/memcontrol.c:6915
mem_cgroup_charge include/linux/memcontrol.h:667 [inline]
__filemap_add_folio+0xe85/0x1ba0 mm/filemap.c:852
filemap_add_folio+0x11d/0x570 mm/filemap.c:934
__filemap_get_folio+0x7cd/0xe30 mm/filemap.c:1976
pagecache_get_page+0x28/0x250 mm/folio-compat.c:110
find_or_create_page include/linux/pagemap.h:613 [inline]
grow_dev_page fs/buffer.c:946 [inline]
grow_buffers fs/buffer.c:1011 [inline]
__getblk_slow fs/buffer.c:1038 [inline]
__getblk_gfp+0x211/0xa20 fs/buffer.c:1333
sb_getblk include/linux/buffer_head.h:356 [inline]
ext4_getblk+0x2a7/0x7c0 fs/ext4/inode.c:874
ext4_bread+0x2a/0x170 fs/ext4/inode.c:920
ext4_append+0x31f/0x5c0 fs/ext4/namei.c:83
ext4_init_new_dir+0x33a/0xa20 fs/ext4/namei.c:2976
ext4_mkdir+0x4f2/0xce0 fs/ext4/namei.c:3022
vfs_mkdir+0x3b6/0x590 fs/namei.c:4036
do_mkdirat+0x260/0x520 fs/namei.c:4061
__do_sys_mkdirat fs/namei.c:4076 [inline]
__se_sys_mkdirat fs/namei.c:4074 [inline]
__x64_sys_mkdirat+0x85/0x90 fs/namei.c:4074
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+0x63/0xcd
RIP: 0033:0x7f226ca8b187
Code: Unable to access opcode bytes at 0x7f226ca8b15d.
RSP: 002b:00007ffc6d1c7a48 EFLAGS: 00000206 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007ffc6d1c7ad0 RCX: 00007f226ca8b187
RDX: 00000000000001ff RSI: 00007ffc6d1c7ad0 RDI: 00000000ffffff9c
RBP: 00007ffc6d1c7aac R08: 0000000000000000 R09: 0000000000000005
R10: 00007ffc6d1c77e5 R11: 0000000000000206 R12: 0000000000000032
R13: 0000000000207946 R14: 0000000000000006 R15: 00007ffc6d1c7b10
</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.