[syzbot] INFO: task hung in __gfs2_trans_begin
From: syzbot
Date: Thu Oct 20 2022 - 02:16:57 EST
Hello,
syzbot found the following issue on:
HEAD commit: 493ffd6605b2 Merge tag 'ucount-rlimits-cleanups-for-v5.19'..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=13aa22ba880000
kernel config: https://syzkaller.appspot.com/x/.config?x=d19f5d16783f901
dashboard link: https://syzkaller.appspot.com/bug?extid=a159cc6676345e04ff7d
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15fbd70c880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14dceee2880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f1ff6481e26f/disk-493ffd66.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/101bd3c7ae47/vmlinux-493ffd66.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/510833e7acb6/mount_1.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+a159cc6676345e04ff7d@xxxxxxxxxxxxxxxxxxxxxxxxx
INFO: task syz-executor714:3609 blocked for more than 143 seconds.
Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor714 state:D stack:23256 pid: 3609 ppid: 3606 flags:0x00004002
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5183 [inline]
__schedule+0x91f/0xdf0 kernel/sched/core.c:6495
schedule+0xcb/0x190 kernel/sched/core.c:6571
rwsem_down_read_slowpath+0x5f9/0x930 kernel/locking/rwsem.c:1087
__down_read_common+0x54/0x2a0 kernel/locking/rwsem.c:1252
__gfs2_trans_begin+0x4e4/0x8c0 fs/gfs2/trans.c:87
gfs2_trans_begin+0x6d/0xe0 fs/gfs2/trans.c:118
gfs2_write_jdata_pagevec+0x100/0xe20 fs/gfs2/aops.c:220
gfs2_write_cache_jdata+0x46d/0x7b0 fs/gfs2/aops.c:349
gfs2_jdata_writepages+0x81/0x150 fs/gfs2/aops.c:391
do_writepages+0x3c3/0x680 mm/page-writeback.c:2469
filemap_fdatawrite_wbc+0x11e/0x170 mm/filemap.c:388
gfs2_ail1_start_one fs/gfs2/log.c:134 [inline]
gfs2_ail1_flush+0xbc3/0xeb0 fs/gfs2/log.c:214
gfs2_ail1_start fs/gfs2/log.c:245 [inline]
empty_ail1_list+0x17f/0x260 fs/gfs2/log.c:977
gfs2_log_flush+0x212a/0x26a0 fs/gfs2/log.c:1122
gfs2_kill_sb+0x50/0xd0 fs/gfs2/ops_fstype.c:1725
deactivate_locked_super+0xa7/0xf0 fs/super.c:331
cleanup_mnt+0x4ce/0x560 fs/namespace.c:1186
task_work_run+0x146/0x1c0 kernel/task_work.c:177
ptrace_notify+0x29a/0x340 kernel/signal.c:2354
ptrace_report_syscall include/linux/ptrace.h:420 [inline]
ptrace_report_syscall_exit include/linux/ptrace.h:482 [inline]
syscall_exit_work+0x8c/0xe0 kernel/entry/common.c:249
syscall_exit_to_user_mode_prepare+0x63/0xc0 kernel/entry/common.c:276
__syscall_exit_to_user_mode_work kernel/entry/common.c:281 [inline]
syscall_exit_to_user_mode+0xa/0x60 kernel/entry/common.c:294
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc8dc1bc527
RSP: 002b:00007fff602f2de8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fc8dc1bc527
RDX: 00007fff602f2ea9 RSI: 000000000000000a RDI: 00007fff602f2ea0
RBP: 00007fff602f2ea0 R08: 00000000ffffffff R09: 00007fff602f2c80
R10: 000055555558c653 R11: 0000000000000206 R12: 00007fff602f3f10
R13: 000055555558c5f0 R14: 00007fff602f2e10 R15: 0000000000000005
</TASK>
INFO: task gfs2_logd:3658 blocked for more than 143 seconds.
Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:gfs2_logd state:D stack:29592 pid: 3658 ppid: 2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5183 [inline]
__schedule+0x91f/0xdf0 kernel/sched/core.c:6495
schedule+0xcb/0x190 kernel/sched/core.c:6571
rwsem_down_write_slowpath+0xf1c/0x1350 kernel/locking/rwsem.c:1182
__down_write_common kernel/locking/rwsem.c:1297 [inline]
__down_write kernel/locking/rwsem.c:1306 [inline]
down_write+0x163/0x170 kernel/locking/rwsem.c:1553
gfs2_log_flush+0xe7/0x26a0 fs/gfs2/log.c:1034
gfs2_logd+0x41f/0xe50 fs/gfs2/log.c:1319
kthread+0x266/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
INFO: task gfs2_quotad:3659 blocked for more than 144 seconds.
Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:gfs2_quotad state:D stack:27576 pid: 3659 ppid: 2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5183 [inline]
__schedule+0x91f/0xdf0 kernel/sched/core.c:6495
schedule+0xcb/0x190 kernel/sched/core.c:6571
rwsem_down_read_slowpath+0x5f9/0x930 kernel/locking/rwsem.c:1087
__down_read_common+0x54/0x2a0 kernel/locking/rwsem.c:1252
__gfs2_trans_begin+0x4e4/0x8c0 fs/gfs2/trans.c:87
gfs2_trans_begin+0x6d/0xe0 fs/gfs2/trans.c:118
gfs2_statfs_sync+0x37f/0x4c0 fs/gfs2/super.c:294
quotad_check_timeo fs/gfs2/quota.c:1512 [inline]
gfs2_quotad+0x485/0xb20 fs/gfs2/quota.c:1554
kthread+0x266/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
INFO: task syz-executor714:3660 blocked for more than 144 seconds.
Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor714 state:D stack:27064 pid: 3660 ppid: 3608 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5183 [inline]
__schedule+0x91f/0xdf0 kernel/sched/core.c:6495
schedule+0xcb/0x190 kernel/sched/core.c:6571
rwsem_down_read_slowpath+0x5f9/0x930 kernel/locking/rwsem.c:1087
__down_read_common+0x54/0x2a0 kernel/locking/rwsem.c:1252
iterate_supers+0xb0/0x1f0 fs/super.c:721
ksys_sync+0xd5/0x1c0 fs/sync.c:104
__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+0x63/0xcd
RIP: 0033:0x7fc8dc1bb189
RSP: 002b:00007fff602f3ed8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 000000000000e657 RCX: 00007fc8dc1bb189
RDX: 00007fc8dc1baba7 RSI: 0000000000000004 RDI: 00007fc8dc1ff074
RBP: 0000000000000000 R08: 00007fff602f3950 R09: 00007fff602f3f00
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff602f3efc
R13: 00007fff602f3f30 R14: 00007fff602f3f10 R15: 0000000000000005
</TASK>
INFO: task syz-executor714:3661 blocked for more than 144 seconds.
Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor714 state:D stack:27288 pid: 3661 ppid: 3610 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5183 [inline]
__schedule+0x91f/0xdf0 kernel/sched/core.c:6495
schedule+0xcb/0x190 kernel/sched/core.c:6571
rwsem_down_read_slowpath+0x5f9/0x930 kernel/locking/rwsem.c:1087
__down_read_common+0x54/0x2a0 kernel/locking/rwsem.c:1252
iterate_supers+0xb0/0x1f0 fs/super.c:721
ksys_sync+0xb7/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+0x63/0xcd
RIP: 0033:0x7fc8dc1bb189
RSP: 002b:00007fff602f3ed8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 000000000000e326 RCX: 00007fc8dc1bb189
RDX: 00007fc8dc1baba7 RSI: 0000000000000004 RDI: 00007fc8dc1ff074
RBP: 0000000000000000 R08: 00007fff602f3950 R09: 00007fff602f3f00
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff602f3efc
R13: 00007fff602f3f30 R14: 00007fff602f3f10 R15: 0000000000000005
</TASK>
INFO: task syz-executor714:3662 blocked for more than 144 seconds.
Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor714 state:D stack:28088 pid: 3662 ppid: 3612 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5183 [inline]
__schedule+0x91f/0xdf0 kernel/sched/core.c:6495
schedule+0xcb/0x190 kernel/sched/core.c:6571
rwsem_down_read_slowpath+0x5f9/0x930 kernel/locking/rwsem.c:1087
__down_read_common+0x54/0x2a0 kernel/locking/rwsem.c:1252
iterate_supers+0xb0/0x1f0 fs/super.c:721
ksys_sync+0xb7/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+0x63/0xcd
RIP: 0033:0x7fc8dc1bb189
RSP: 002b:00007fff602f3ed8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 000000000000e34d RCX: 00007fc8dc1bb189
RDX: 00007fc8dc1baba7 RSI: 0000000000000004 RDI: 00007fc8dc1ff074
RBP: 0000000000000000 R08: 00007fff602f3950 R09: 00007fff602f3f00
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff602f3efc
R13: 00007fff602f3f30 R14: 00007fff602f3f10 R15: 0000000000000005
</TASK>
INFO: task syz-executor714:3663 blocked for more than 144 seconds.
Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor714 state:D stack:28088 pid: 3663 ppid: 3607 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5183 [inline]
__schedule+0x91f/0xdf0 kernel/sched/core.c:6495
schedule+0xcb/0x190 kernel/sched/core.c:6571
rwsem_down_read_slowpath+0x5f9/0x930 kernel/locking/rwsem.c:1087
__down_read_common+0x54/0x2a0 kernel/locking/rwsem.c:1252
iterate_supers+0xb0/0x1f0 fs/super.c:721
ksys_sync+0xb7/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+0x63/0xcd
RIP: 0033:0x7fc8dc1bb189
RSP: 002b:00007fff602f3ed8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 000000000000e673 RCX: 00007fc8dc1bb189
RDX: 00007fc8dc1baba7 RSI: 0000000000000004 RDI: 00007fc8dc1ff074
RBP: 0000000000000000 R08: 00007fff602f3950 R09: 00007fff602f3f00
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff602f3efc
R13: 00007fff602f3f30 R14: 00007fff602f3f10 R15: 0000000000000005
</TASK>
INFO: task syz-executor714:3664 blocked for more than 145 seconds.
Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor714 state:D stack:28088 pid: 3664 ppid: 3611 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5183 [inline]
__schedule+0x91f/0xdf0 kernel/sched/core.c:6495
schedule+0xcb/0x190 kernel/sched/core.c:6571
rwsem_down_read_slowpath+0x5f9/0x930 kernel/locking/rwsem.c:1087
__down_read_common+0x54/0x2a0 kernel/locking/rwsem.c:1252
iterate_supers+0xb0/0x1f0 fs/super.c:721
ksys_sync+0xb7/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+0x63/0xcd
RIP: 0033:0x7fc8dc1bb189
RSP: 002b:00007fff602f3ed8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 000000000000e62e RCX: 00007fc8dc1bb189
RDX: 00007fc8dc1baba7 RSI: 0000000000000004 RDI: 00007fc8dc1ff074
RBP: 0000000000000000 R08: 00007fff602f3950 R09: 00007fff602f3f00
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff602f3efc
R13: 00007fff602f3f30 R14: 00007fff602f3f10 R15: 0000000000000005
</TASK>
INFO: lockdep is turned off.
NMI backtrace for cpu 0
CPU: 0 PID: 29 Comm: khungtaskd Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106
nmi_cpu_backtrace+0x425/0x450 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x169/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xcd5/0xd20 kernel/hung_task.c:369
kthread+0x266/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: 1081 Comm: kworker/u4:5 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:__sanitizer_cov_trace_switch+0x0/0x100 kernel/kcov.c:310
Code: 48 83 c8 08 48 c7 04 01 07 00 00 00 48 89 d0 48 83 c8 10 48 89 3c 01 48 83 ca 18 48 89 34 11 4e 89 44 c9 20 c3 0f 1f 44 00 00 <41> 57 41 56 53 48 8b 46 08 48 83 c0 f8 48 c1 c0 3d 48 83 f8 07 0f
RSP: 0018:ffffc9000515f810 EFLAGS: 00000246
RAX: 1ffff92000a2bf00 RBX: 0000000000000001 RCX: 0000000000000000
RDX: ffff8880200fd880 RSI: ffffffff8d1c1900 RDI: 0000000000000001
RBP: 0000000000000000 R08: ffffffff846979e0 R09: ffffc9000515f960
R10: fffff52000a2bf37 R11: 1ffff92000a2bf2c R12: ffffc9000515f960
R13: 0000000000000044 R14: 1ffff92000a2bf39 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055c30a147990 CR3: 000000000c88e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
insn_get_displacement+0x33b/0x9a0 arch/x86/lib/insn.c:490
insn_get_immediate+0x427/0x12e0 arch/x86/lib/insn.c:632
insn_get_length arch/x86/lib/insn.c:707 [inline]
insn_decode+0x3b0/0x550 arch/x86/lib/insn.c:747
text_poke_loc_init+0xb3/0x500 arch/x86/kernel/alternative.c:1590
arch_jump_label_transform_queue+0x70/0xd0 arch/x86/kernel/jump_label.c:138
__jump_label_update+0x19b/0x3b0 kernel/jump_label.c:447
static_key_disable_cpuslocked+0xc8/0x1b0 kernel/jump_label.c:207
static_key_disable+0x16/0x20 kernel/jump_label.c:215
toggle_allocation_gate+0x3b8/0x450 mm/kfence/core.c:825
process_one_work+0x877/0xdb0 kernel/workqueue.c:2289
worker_thread+0xb14/0x1330 kernel/workqueue.c:2436
kthread+0x266/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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 syzkaller@xxxxxxxxxxxxxxxx.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches