[v6.6] BUG: sleeping function called from invalid context in gfs2_withdraw

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13fb0f82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=3cdbdd888aae950489a5
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/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz

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

syz-executor: attempt to access beyond end of device
loop5: rw=1, sector=8192, nr_sectors = 4 limit=64
gfs2: fsid=syz:syz.0: Error 10 writing to journal, jid=0
gfs2: fsid=syz:syz.0: fatal: I/O error(s)
gfs2: fsid=syz:syz.0: about to withdraw this file system
BUG: sleeping function called from invalid context at fs/gfs2/util.c:159
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 7179, name: syz-executor
preempt_count: 1, expected: 0
RCU nest depth: 0, expected: 0
4 locks held by syz-executor/7179:
#0: ffff88807d2cc0e0 (&type->s_umount_key#80){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807d2cc0e0 (&type->s_umount_key#80){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807d2cc0e0 (&type->s_umount_key#80){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffff888064045060 (&sdp->sd_log_flush_lock){++++}-{3:3}, at: gfs2_log_flush+0x104/0x24b0 fs/gfs2/log.c:1042
#2: ffff888064044e88 (&sdp->sd_log_lock){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline]
#2: ffff888064044e88 (&sdp->sd_log_lock){+.+.}-{2:2}, at: gfs2_log_lock fs/gfs2/log.h:32 [inline]
#2: ffff888064044e88 (&sdp->sd_log_lock){+.+.}-{2:2}, at: gfs2_flush_revokes+0x52/0x80 fs/gfs2/log.c:814
#3: ffff888064045248 (&sdp->sd_freeze_mutex){+.+.}-{3:3}, at: signal_our_withdraw fs/gfs2/util.c:152 [inline]
#3: ffff888064045248 (&sdp->sd_freeze_mutex){+.+.}-{3:3}, at: gfs2_withdraw+0x413/0x14b0 fs/gfs2/util.c:342
Preemption disabled at:
[<0000000000000000>] 0x0
CPU: 0 PID: 7179 Comm: syz-executor Not tainted 6.6.100-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
__might_resched+0x491/0x610 kernel/sched/core.c:10209
signal_our_withdraw fs/gfs2/util.c:157 [inline]
gfs2_withdraw+0x461/0x14b0 fs/gfs2/util.c:342
gfs2_ail1_empty+0x7be/0x850 fs/gfs2/log.c:377
gfs2_flush_revokes+0x5c/0x80 fs/gfs2/log.c:815
revoke_lo_before_commit+0x2c/0x5f0 fs/gfs2/lops.c:867
lops_before_commit fs/gfs2/lops.h:42 [inline]
gfs2_log_flush+0xb84/0x24b0 fs/gfs2/log.c:1102
gfs2_kill_sb+0x5d/0x320 fs/gfs2/ops_fstype.c:1789
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f93f778fcd7
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffc48b5fdd8 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000064 RCX: 00007f93f778fcd7
RDX: 0000000000000200 RSI: 0000000000000009 RDI: 00007ffc48b60f80
RBP: 00007f93f7810b55 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000100 R11: 0000000000000206 R12: 00007ffc48b60f80
R13: 00007f93f7810b55 R14: 0000555563cd34a8 R15: 00007ffc48b62050
</TASK>
BUG: scheduling while atomic: syz-executor/7179/0x00000002
4 locks held by syz-executor/7179:
#0: ffff88807d2cc0e0 (&type->s_umount_key#80){+.+.}-{3:3}, at: __super_lock fs/super.c:56 [inline]
#0: ffff88807d2cc0e0 (&type->s_umount_key#80){+.+.}-{3:3}, at: __super_lock_excl fs/super.c:71 [inline]
#0: ffff88807d2cc0e0 (&type->s_umount_key#80){+.+.}-{3:3}, at: deactivate_super+0xa4/0xe0 fs/super.c:513
#1: ffff888064045060 (&sdp->sd_log_flush_lock){++++}-{3:3}, at: gfs2_log_flush+0x104/0x24b0 fs/gfs2/log.c:1042
#2: ffff888064044e88 (&sdp->sd_log_lock){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline]
#2: ffff888064044e88 (&sdp->sd_log_lock){+.+.}-{2:2}, at: gfs2_log_lock fs/gfs2/log.h:32 [inline]
#2: ffff888064044e88 (&sdp->sd_log_lock){+.+.}-{2:2}, at: gfs2_flush_revokes+0x52/0x80 fs/gfs2/log.c:814
#3: ffff888064045248 (&sdp->sd_freeze_mutex){+.+.}-{3:3}, at: signal_our_withdraw fs/gfs2/util.c:152 [inline]
#3: ffff888064045248 (&sdp->sd_freeze_mutex){+.+.}-{3:3}, at: gfs2_withdraw+0x413/0x14b0 fs/gfs2/util.c:342
Modules linked in:
Preemption disabled at:
[<0000000000000000>] 0x0


---
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