[v6.6] WARNING in __folio_mark_dirty

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c2603c511feb Linux 6.6.93
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1245e90c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=486bade17c8c30b9
dashboard link: https://syzkaller.appspot.com/bug?extid=d429f1fb4bc9f0306658
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8754f950a6e7/disk-c2603c51.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b19332dbf63/vmlinux-c2603c51.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb245e836038/bzImage-c2603c51.xz

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

gfs2: fsid=syz:syz.0: first mount done, others may mount
gfs2: fsid=syz:syz.0: found 1 quota changes
------------[ cut here ]------------
WARNING: CPU: 1 PID: 15240 at include/linux/backing-dev.h:256 inode_to_wb include/linux/backing-dev.h:252 [inline]
WARNING: CPU: 1 PID: 15240 at include/linux/backing-dev.h:256 folio_account_dirtied mm/page-writeback.c:2640 [inline]
WARNING: CPU: 1 PID: 15240 at include/linux/backing-dev.h:256 __folio_mark_dirty+0x912/0x1110 mm/page-writeback.c:2691
Modules linked in:
CPU: 1 PID: 15240 Comm: syz.4.2586 Not tainted 6.6.93-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:inode_to_wb include/linux/backing-dev.h:252 [inline]
RIP: 0010:folio_account_dirtied mm/page-writeback.c:2640 [inline]
RIP: 0010:__folio_mark_dirty+0x912/0x1110 mm/page-writeback.c:2691
Code: e9 92 f8 ff ff e8 de bf cd ff 0f 0b e9 d9 f8 ff ff e8 d2 bf cd ff 48 89 df 48 8b 74 24 28 e8 e5 c3 2d 00 eb a6 e8 be bf cd ff <0f> 0b e9 84 fb ff ff 89 c2 80 e2 07 80 c2 03 38 ca 0f 8c f2 f8 ff
RSP: 0018:ffffc900034f7480 EFLAGS: 00010083
RAX: ffffffff81b7d722 RBX: ffffea00017bb140 RCX: 0000000000080000
RDX: ffffc90017c2b000 RSI: 000000000001f888 RDI: 000000000001f889
RBP: 0000000000000001 R08: ffffea00017bb147 R09: 1ffffd40002f7628
R10: dffffc0000000000 R11: fffff940002f7629 R12: 1ffff11003f9c6c1
R13: ffff88801fce3490 R14: 0000000000000000 R15: ffff88801fce3608
FS: 00007f61b5b916c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f762cfbf000 CR3: 000000006346c000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
mark_buffer_dirty+0x26e/0x4d0 fs/buffer.c:1212
gfs2_unpin+0x125/0x9a0 fs/gfs2/lops.c:111
buf_lo_after_commit+0x15e/0x1b0 fs/gfs2/lops.c:745
lops_after_commit fs/gfs2/lops.h:51 [inline]
gfs2_log_flush+0x1094/0x24b0 fs/gfs2/log.c:1117
gfs2_write_inode+0x23f/0x3d0 fs/gfs2/super.c:457
write_inode fs/fs-writeback.c:1473 [inline]
__writeback_single_inode+0x705/0xee0 fs/fs-writeback.c:1690
writeback_single_inode+0x211/0x720 fs/fs-writeback.c:1746
sync_inode_metadata+0xba/0x110 fs/fs-writeback.c:2811
gfs2_fsync+0x1b6/0x350 fs/gfs2/file.c:762
__gfs2_fallocate+0x18bd/0x1c00 fs/gfs2/file.c:1349
gfs2_fallocate+0x344/0x470 fs/gfs2/file.c:1395
vfs_fallocate+0x58e/0x700 fs/open.c:324
ksys_fallocate fs/open.c:347 [inline]
__do_sys_fallocate fs/open.c:355 [inline]
__se_sys_fallocate fs/open.c:353 [inline]
__x64_sys_fallocate+0xc1/0x110 fs/open.c:353
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f61b4d8e929
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:00007f61b5b91038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007f61b4fb5fa0 RCX: 00007f61b4d8e929
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007f61b4e10b39 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000001000f4 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f61b4fb5fa0 R15: 00007ffec8e36728
</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: c2603c511feb Linux 6.6.93
git tree: linux-6.6.y

console output: https://syzkaller.appspot.com/x/log.txt?x=131a750c580000

kernel config: https://syzkaller.appspot.com/x/.config?x=486bade17c8c30b9
dashboard link: https://syzkaller.appspot.com/bug?extid=d429f1fb4bc9f0306658
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=167dd5d4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14292370580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8754f950a6e7/disk-c2603c51.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b19332dbf63/vmlinux-c2603c51.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb245e836038/bzImage-c2603c51.xz

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

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

gfs2: fsid=syz:syz.0: first mount done, others may mount

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5772 at include/linux/backing-dev.h:256 inode_to_wb include/linux/backing-dev.h:252 [inline]
WARNING: CPU: 1 PID: 5772 at include/linux/backing-dev.h:256 folio_account_dirtied mm/page-writeback.c:2640 [inline]
WARNING: CPU: 1 PID: 5772 at include/linux/backing-dev.h:256 __folio_mark_dirty+0x912/0x1110 mm/page-writeback.c:2691
Modules linked in:
CPU: 1 PID: 5772 Comm: syz-executor227 Not tainted 6.6.93-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:inode_to_wb include/linux/backing-dev.h:252 [inline]
RIP: 0010:folio_account_dirtied mm/page-writeback.c:2640 [inline]
RIP: 0010:__folio_mark_dirty+0x912/0x1110 mm/page-writeback.c:2691
Code: e9 92 f8 ff ff e8 de bf cd ff 0f 0b e9 d9 f8 ff ff e8 d2 bf cd ff 48 89 df 48 8b 74 24 28 e8 e5 c3 2d 00 eb a6 e8 be bf cd ff <0f> 0b e9 84 fb ff ff 89 c2 80 e2 07 80 c2 03 38 ca 0f 8c f2 f8 ff

RSP: 0018:ffffc9000418f8c0 EFLAGS: 00010093
RAX: ffffffff81b7d722 RBX: ffffea0001d56fc0 RCX: ffff88802d49bc00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000001 R08: ffff888148c71f0f R09: 1ffff1102918e3e1
R10: dffffc0000000000 R11: ffffed102918e3e2 R12: 1ffff1102918e3e1
R13: ffff888148c71d90 R14: 0000000000000000 R15: ffff888148c71f08
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007f60b9418000 CR3: 000000002d6c0000 CR4: 00000000003506e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
mark_buffer_dirty+0x26e/0x4d0 fs/buffer.c:1212
gfs2_unpin+0x125/0x9a0 fs/gfs2/lops.c:111
buf_lo_after_commit+0x15e/0x1b0 fs/gfs2/lops.c:745
lops_after_commit fs/gfs2/lops.h:51 [inline]
gfs2_log_flush+0x1094/0x24b0 fs/gfs2/log.c:1117

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
exit_task_work include/linux/task_work.h:43 [inline]
do_exit+0x903/0x23c0 kernel/exit.c:874
do_group_exit+0x21b/0x2d0 kernel/exit.c:1023
__do_sys_exit_group kernel/exit.c:1034 [inline]
__se_sys_exit_group kernel/exit.c:1032 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1032

do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2

RIP: 0033:0x7fddfc03bb09
Code: Unable to access opcode bytes at 0x7fddfc03badf.
RSP: 002b:00007ffd961434f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fddfc03bb09
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007fddfc0f02b0 R08: ffffffffffffffb8 R09: 0000000000000006
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fddfc0f02b0
R13: 0000000000000000 R14: 00007fddfc0f1020 R15: 00007fddfc00a060
</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.

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit ae9f3bd8259a0a8f67be2420e66bb05fbb95af48
git tree: upstream
Author: Andreas Gruenbacher <agru...@redhat.com>
Date: Sat Apr 5 22:31:37 2025 +0000

gfs2: replace sd_aspace with sd_inode

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1079ea58580000

kernel config: https://syzkaller.appspot.com/x/.config?x=486bade17c8c30b9
dashboard link: https://syzkaller.appspot.com/bug?extid=d429f1fb4bc9f0306658

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=167dd5d4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14292370580000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection