[v5.15] INFO: task hung in gfs2_statfs_init

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12ae9c42580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=9e1baec56c90d4d3d54f
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fa511d2a8893/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f14b6c77bbb9/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/388987ba15c6/bzImage-c7964837.xz

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

INFO: task syz.0.52:4557 blocked for more than 144 seconds.
Not tainted 5.15.189-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.52 state:D stack:24960 pid: 4557 ppid: 4185 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x11b8/0x43b0 kernel/sched/core.c:6376
schedule+0x11b/0x1e0 kernel/sched/core.c:6459
bit_wait+0xd/0xc0 kernel/sched/wait_bit.c:199
__wait_on_bit kernel/sched/wait_bit.c:49 [inline]
out_of_line_wait_on_bit+0x15e/0x200 kernel/sched/wait_bit.c:64
wait_on_bit include/linux/wait_bit.h:76 [inline]
gfs2_glock_wait+0xd9/0x1c0 fs/gfs2/glock.c:1282
gfs2_glock_nq_init fs/gfs2/glock.h:246 [inline]
gfs2_statfs_init+0xf9/0x490 fs/gfs2/super.c:190
gfs2_fill_super+0x1749/0x1f50 fs/gfs2/ops_fstype.c:1257
get_tree_bdev+0x3f1/0x610 fs/super.c:1325
gfs2_get_tree+0x4d/0x1e0 fs/gfs2/ops_fstype.c:1332
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3014
do_mount fs/namespace.c:3357 [inline]
__do_sys_mount fs/namespace.c:3565 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3542
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f6996b1538a
RSP: 002b:00007f6994d7ae68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f6994d7aef0 RCX: 00007f6996b1538a
RDX: 0000200000000400 RSI: 0000200000012500 RDI: 00007f6994d7aeb0
RBP: 0000200000000400 R08: 00007f6994d7aef0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000200000012500
R13: 00007f6994d7aeb0 R14: 00000000000125e1 R15: 00002000000000c0
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c360 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3948:
#0: ffff88814c67d098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900025e62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
3 locks held by kworker/1:4/4252:
#0: ffff888144baf938 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000376fd00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff888024221220 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:760 [inline]
#2: ffff888024221220 (&dev->mutex){....}-{3:3}, at: hub_event+0x18f/0x4fa0 drivers/usb/core/hub.c:5781
1 lock held by syz.0.52/4557:
#0: ffff8880766b60e0 (&type->s_umount_key#75/1){+.+.}-{3:3}, at: alloc_super+0x201/0x950 fs/super.c:229
2 locks held by syz.5.313/5918:

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/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+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4371 Comm: kworker/u4:19 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4702 [inline]
RIP: 0010:__lock_acquire+0x6e7/0x7c60 kernel/locking/lockdep.c:4962
Code: fe 0f 88 70 01 00 00 44 89 fb 81 e3 ff ff ff 7f 83 f8 31 73 43 48 8d 04 9b 49 8d 5c c5 00 48 89 d8 48 c1 e8 03 42 0f b6 04 00 <84> c0 75 45 8b 1b 48 8b 44 24 58 42 0f b6 04 00 84 c0 75 55 48 8b
RSP: 0018:ffffc90004537780 EFLAGS: 00000806
RAX: 0000000000000000 RBX: ffff8880272fc6b8 RCX: 0000000000000002
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8ffb71b0
RBP: ffffc900045379d0 R08: dffffc0000000000 R09: fffffbfff1ff6e37
R10: fffffbfff1ff6e37 R11: 1ffffffff1ff6e36 R12: 0000000000000000
R13: ffff8880272fc690 R14: 0000000000000003 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5f16fb7000 CR3: 0000000023c30000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x32/0x50 kernel/locking/spinlock.c:178
spin_lock_bh include/linux/spinlock.h:368 [inline]
batadv_nc_purge_paths+0xe7/0x3b0 net/batman-adv/network-coding.c:446
batadv_nc_worker+0x327/0x5c0 net/batman-adv/network-coding.c:726
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=14a6c462580000

kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=9e1baec56c90d4d3d54f
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12d76462580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10459c42580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fa511d2a8893/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f14b6c77bbb9/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/388987ba15c6/bzImage-c7964837.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/f54229392779/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=14d76462580000)

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

INFO: task syz.0.17:4331 blocked for more than 143 seconds.

Not tainted 5.15.189-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz.0.17 state:D stack:23648 pid: 4331 ppid: 4313 flags:0x00004004

Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x11b8/0x43b0 kernel/sched/core.c:6376
schedule+0x11b/0x1e0 kernel/sched/core.c:6459
bit_wait+0xd/0xc0 kernel/sched/wait_bit.c:199
__wait_on_bit kernel/sched/wait_bit.c:49 [inline]
out_of_line_wait_on_bit+0x15e/0x200 kernel/sched/wait_bit.c:64
wait_on_bit include/linux/wait_bit.h:76 [inline]
gfs2_glock_wait+0xd9/0x1c0 fs/gfs2/glock.c:1282
gfs2_glock_nq_init fs/gfs2/glock.h:246 [inline]
gfs2_statfs_init+0xf9/0x490 fs/gfs2/super.c:190
gfs2_fill_super+0x1749/0x1f50 fs/gfs2/ops_fstype.c:1257
get_tree_bdev+0x3f1/0x610 fs/super.c:1325
gfs2_get_tree+0x4d/0x1e0 fs/gfs2/ops_fstype.c:1332
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3014
do_mount fs/namespace.c:3357 [inline]
__do_sys_mount fs/namespace.c:3565 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3542
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0

RIP: 0033:0x7fa57876f38a
RSP: 002b:00007ffdef3cbdf8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffdef3cbe80 RCX: 00007fa57876f38a
RDX: 0000200000000400 RSI: 0000200000012500 RDI: 00007ffdef3cbe40
RBP: 0000200000000400 R08: 00007ffdef3cbe80 R09: 0000000000000000

R10: 0000000000000000 R11: 0000000000000246 R12: 0000200000012500

R13: 00007ffdef3cbe40 R14: 00000000000125e1 R15: 00002000000000c0

</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c360
(
rcu_read_lock
){....}-{1:2}
, at: rcu_lock_acquire+0x0/0x30

2 locks held by getty/3944:
#0:
ffff88802c293098
(
&tty->ldisc_sem

){++++}-{0:0}
, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1:

ffffc90002d032e8

(&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158

1 lock held by syz.0.17/4331:
#0: ffff88807cd8c0e0 (&type->s_umount_key#53/1){+.+.}-{3:3}, at: alloc_super+0x201/0x950 fs/super.c:229
2 locks held by syz.1.219/4571:
#0: ffff88801fe3ad18 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xf9/0x7d0 block/bdev.c:915
#1: ffff88802026c468 (&lo->lo_mutex){+.+.}-{3:3}, at: lo_release+0x4d/0x1f0 drivers/block/loop.c:2071

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/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+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0

CPU: 0 PID: 9 Comm: kworker/u4:0 Not tainted 5.15.189-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025

Workqueue: phy7 ieee80211_iface_work
RIP: 0010:rdtsc_ordered arch/x86/include/asm/msr.h:224 [inline]
RIP: 0010:pvclock_clocksource_read+0xe7/0x760 arch/x86/kernel/pvclock.c:76
Code: df 48 89 54 24 38 4c 89 74 24 28 42 0f b6 04 22 84 c0 0f 85 45 01 00 00 43 0f b6 04 26 84 c0 0f 85 7f 01 00 00 8b 1f 0f 01 f9 <66> 90 48 89 d5 48 8b 8c 24 90 00 00 00 42 0f b6 0c 21 84 c9 0f 85
RSP: 0018:ffffc90000ce79c0 EFLAGS: 00000046
RAX: 0000000005e46072 RBX: 0000000000000006 RCX: 0000000000000000
RDX: 000000000000009b RSI: ffffffff8eecc01c RDI: ffffffff8eecc000
RBP: ffff88801b74d940 R08: ffffffff8eecc008 R09: ffffffff8eecc018
R10: ffffffff8eecc010 R11: ffffffff8eecc003 R12: dffffc0000000000
R13: ffff88801b74ec38 R14: 1ffffffff1dd9800 R15: 0000000000000000

FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f6cc1279000 CR3: 000000005bf63000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>

kvm_clock_read arch/x86/kernel/kvmclock.c:79 [inline]
kvm_sched_clock_read+0x14/0x40 arch/x86/kernel/kvmclock.c:91
sched_clock_cpu+0x15/0x3c0 kernel/sched/clock.c:371
cpu_clock include/linux/sched/clock.h:79 [inline]
psi_task_change+0xe5/0x340 kernel/sched/psi.c:813
psi_enqueue kernel/sched/stats.h:102 [inline]
enqueue_task+0x26d/0x2b0 kernel/sched/core.c:1973
activate_task kernel/sched/core.c:2005 [inline]
ttwu_do_activate+0x1b5/0x380 kernel/sched/core.c:3614
ttwu_queue kernel/sched/core.c:3823 [inline]
try_to_wake_up+0x618/0x1050 kernel/sched/core.c:4146
wake_up_worker kernel/workqueue.c:859 [inline]
process_one_work+0x69c/0x1000 kernel/workqueue.c:2273

worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>


---

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.