syzbot


BUG: sleeping function called from invalid context in gfs2_withdraw

Status: upstream: reported on 2025/10/27 10:36
Reported-by: syzbot+b4bd4abe9a82a8cafb61@syzkaller.appspotmail.com
First crash: 7d09h, last: 7d09h
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 BUG: sleeping function called from invalid context in gfs2_withdraw origin:upstream 5 C error 15 9d19h 225d 0/3 upstream: reported C repro on 2025/03/23 18:44
upstream BUG: sleeping function called from invalid context in gfs2_withdraw gfs2 5 C error done 182 665d 785d 25/29 fixed on 2024/03/20 11:33
upstream BUG: sleeping function called from invalid context in gfs2_withdraw (2) gfs2 5 11 1d20h 50d 0/29 upstream: reported on 2025/09/13 22:07
linux-6.6 BUG: sleeping function called from invalid context in gfs2_withdraw 5 9 11d 96d 0/2 upstream: reported on 2025/07/30 20:12

Sample crash report:
BUG: sleeping function called from invalid context at include/linux/wait_bit.h:73
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5222, name: syz.6.125
5 locks held by syz.6.125/5222:
 #0: ffff888029ea99f0 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2bf/0x370 fs/file.c:1056
 #1: ffff8880749dc460 (sb_writers#22){.+.+}-{0:0}, at: vfs_write+0x28a/0xd00 fs/read_write.c:590
 #2: ffff88805fbaedd0 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #2: ffff88805fbaedd0 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: gfs2_file_write_iter+0x33b/0x11d0 fs/gfs2/file.c:1123
 #3: ffff88807d7210a8 (&sdp->sd_log_flush_lock){++++}-{3:3}, at: gfs2_log_flush+0xdb/0x2610 fs/gfs2/log.c:1035
 #4: ffff88807d720ed0 (&sdp->sd_log_lock){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:364 [inline]
 #4: ffff88807d720ed0 (&sdp->sd_log_lock){+.+.}-{2:2}, at: gfs2_log_lock fs/gfs2/log.h:32 [inline]
 #4: ffff88807d720ed0 (&sdp->sd_log_lock){+.+.}-{2:2}, at: gfs2_flush_revokes+0x4e/0x80 fs/gfs2/log.c:806
Preemption disabled at:
[<0000000000000000>] 0x0
CPU: 1 PID: 5222 Comm: syz.6.125 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 ___might_sleep+0x47c/0x600 kernel/sched/core.c:9658
 wait_on_bit include/linux/wait_bit.h:73 [inline]
 gfs2_withdraw+0x28b/0x1460 fs/gfs2/util.c:332
 gfs2_ail1_empty+0x7c2/0x850 fs/gfs2/log.c:369
 gfs2_flush_revokes+0x58/0x80 fs/gfs2/log.c:807
 revoke_lo_before_commit+0x28/0x5f0 fs/gfs2/lops.c:872
 lops_before_commit fs/gfs2/lops.h:40 [inline]
 gfs2_log_flush+0xbff/0x2610 fs/gfs2/log.c:1094
 gfs2_write_inode+0x2a5/0x430 fs/gfs2/super.c:439
 write_inode fs/fs-writeback.c:1505 [inline]
 __writeback_single_inode+0x6c3/0xda0 fs/fs-writeback.c:1715
 writeback_single_inode+0x221/0x8b0 fs/fs-writeback.c:1770
 sync_inode_metadata+0xa8/0xf0 fs/fs-writeback.c:2831
 gfs2_fsync+0x1b2/0x340 fs/gfs2/file.c:765
 generic_write_sync+0xa2/0xf0 include/linux/fs.h:2989
 gfs2_file_write_iter+0xf64/0x11d0 fs/gfs2/file.c:1159
 call_write_iter include/linux/fs.h:2172 [inline]
 new_sync_write fs/read_write.c:507 [inline]
 vfs_write+0x712/0xd00 fs/read_write.c:594
 ksys_write+0x14d/0x250 fs/read_write.c:647
 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:0x7fc7a6808fc9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc7a4a70038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fc7a6a5ffa0 RCX: 00007fc7a6808fc9
RDX: 00000000ffffffd7 RSI: 0000200000000000 RDI: 0000000000000005
RBP: 00007fc7a688bf91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc7a6a60038 R14: 00007fc7a6a5ffa0 R15: 00007ffcd7f34128
 </TASK>
BUG: scheduling while atomic: syz.6.125/5222/0x00000002
5 locks held by syz.6.125/5222:
 #0: ffff888029ea99f0 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2bf/0x370 fs/file.c:1056
 #1: ffff8880749dc460 (sb_writers#22){.+.+}-{0:0}, at: vfs_write+0x28a/0xd00 fs/read_write.c:590
 #2: ffff88805fbaedd0 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
 #2: ffff88805fbaedd0 (&sb->s_type->i_mutex_key#28){+.+.}-{3:3}, at: gfs2_file_write_iter+0x33b/0x11d0 fs/gfs2/file.c:1123
 #3: ffff88807d7210a8 (&sdp->sd_log_flush_lock){++++}-{3:3}, at: gfs2_log_flush+0xdb/0x2610 fs/gfs2/log.c:1035
 #4: ffff88807d720ed0 (&sdp->sd_log_lock){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:364 [inline]
 #4: ffff88807d720ed0 (&sdp->sd_log_lock){+.+.}-{2:2}, at: gfs2_log_lock fs/gfs2/log.h:32 [inline]
 #4: ffff88807d720ed0 (&sdp->sd_log_lock){+.+.}-{2:2}, at: gfs2_flush_revokes+0x4e/0x80 fs/gfs2/log.c:806
Modules linked in:
Preemption disabled at:
[<0000000000000000>] 0x0

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/10/27 10:35 linux-5.15.y ac56c046adf4 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: sleeping function called from invalid context in gfs2_withdraw
* Struck through repros no longer work on HEAD.