[v5.15] WARNING in f2fs_fill_super

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: eceeec79dbc6 Linux 5.15.210
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16b4e8ea580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a0cae3abafc69
dashboard link: https://syzkaller.appspot.com/bug?extid=4ed06283532ebfd44de7
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a8f82a67235a/disk-eceeec79.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f10abb6026a6/vmlinux-eceeec79.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ade6c70761ba/bzImage-eceeec79.xz

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

F2FS-fs (loop3): LFS not compatible with checkpoint=disable
------------[ cut here ]------------
WARNING: CPU: 1 PID: 5543 at kernel/locking/lockdep.c:6325 lockdep_unregister_key+0x4d7/0x520 kernel/locking/lockdep.c:6334
Modules linked in:
CPU: 1 PID: 5543 Comm: syz.3.909 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:lockdep_unregister_key+0x4d7/0x520 kernel/locking/lockdep.c:6325
Code: 80 00 00 00 75 39 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 f9 57 5c 08 41 f7 c4 00 02 00 00 74 90 fb 84 db 75 8f eb a0 <0f> 0b e9 44 ff ff ff 0f 0b e9 b0 fe ff ff 0f 0b e9 fd fe ff ff e8
RSP: 0018:ffffc900034af9c0 EFLAGS: 00010002
RAX: 0000000000000000 RBX: ffff88802752d728 RCX: dffffc0000000000
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffc900034af940
RBP: ffffc900034afa90 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000695f28 R12: 0000000000000a06
R13: ffff88802752c000 R14: 0000000000000000 R15: 1ffff92000695f3c
FS: 00007fa6256936c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32219ff8 CR3: 0000000057fea000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
f2fs_fill_super+0x3ce4/0x7050 fs/f2fs/super.c:4536
mount_bdev+0x28a/0x3c0 fs/super.c:1400
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x247/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
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:0x7fa62743b0ca
Code: 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa625692e58 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fa625692ee0 RCX: 00007fa62743b0ca
RDX: 0000200000000200 RSI: 0000200000000040 RDI: 00007fa625692ea0
RBP: 0000200000000200 R08: 00007fa625692ee0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000200000000040
R13: 00007fa625692ea0 R14: 0000000000005511 R15: 00002000000003c0
</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: eceeec79dbc6 Linux 5.15.210
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=1314dba1580000

kernel config: https://syzkaller.appspot.com/x/.config?x=6a0cae3abafc69
dashboard link: https://syzkaller.appspot.com/bug?extid=4ed06283532ebfd44de7
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10be177a580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a8f82a67235a/disk-eceeec79.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f10abb6026a6/vmlinux-eceeec79.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ade6c70761ba/bzImage-eceeec79.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/1e27bc04b648/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=16ad0356580000)

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

loop0: detected capacity change from 0 to 40427
F2FS-fs (loop0): quotafile must be on filesystem root
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4364 at kernel/locking/lockdep.c:6325 lockdep_unregister_key+0x4d7/0x520 kernel/locking/lockdep.c:6334
Modules linked in:
CPU: 1 PID: 4364 Comm: syz.0.17 Not tainted syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:lockdep_unregister_key+0x4d7/0x520 kernel/locking/lockdep.c:6325
Code: 80 00 00 00 75 39 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 f9 57 5c 08 41 f7 c4 00 02 00 00 74 90 fb 84 db 75 8f eb a0 <0f> 0b e9 44 ff ff ff 0f 0b e9 b0 fe ff ff 0f 0b e9 fd fe ff ff e8

RSP: 0018:ffffc900033af9c0 EFLAGS: 00010002
RAX: 0000000000000000 RBX: ffff88807a465728 RCX: dffffc0000000000
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffc900033af940
RBP: ffffc900033afa90 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000675f28 R12: 0000000000000206
R13: ffff88807a464000 R14: 0000000000000000 R15: 1ffff92000675f3c
FS: 00007f3ffbf926c0(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000

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

CR2: 00007fa2d1992000 CR3: 00000000717ab000 CR4: 00000000003506e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
f2fs_fill_super+0x3ce4/0x7050 fs/f2fs/super.c:4536
mount_bdev+0x28a/0x3c0 fs/super.c:1400
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x247/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
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:0x7f3ffc9320ca

Code: 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48

RSP: 002b:00007f3ffbf91e58 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f3ffbf91ee0 RCX: 00007f3ffc9320ca
RDX: 0000200000000600 RSI: 00002000000000c0 RDI: 00007f3ffbf91ea0
RBP: 0000200000000600 R08: 00007f3ffbf91ee0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00002000000000c0
R13: 00007f3ffbf91ea0 R14: 0000000000005510 R15: 0000200000000840
</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 has found a reproducer for the following issue on:

HEAD commit: eceeec79dbc6 Linux 5.15.210
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=10edebb6580000

kernel config: https://syzkaller.appspot.com/x/.config?x=6a0cae3abafc69
dashboard link: https://syzkaller.appspot.com/bug?extid=4ed06283532ebfd44de7
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=161962fe580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=169e87b6580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a8f82a67235a/disk-eceeec79.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f10abb6026a6/vmlinux-eceeec79.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ade6c70761ba/bzImage-eceeec79.xz

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

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

loop0: detected capacity change from 0 to 40427

------------[ cut here ]------------
WARNING: CPU: 0 PID: 4324 at kernel/locking/lockdep.c:6325 lockdep_unregister_key+0x4d7/0x520 kernel/locking/lockdep.c:6334
Modules linked in:
CPU: 0 PID: 4324 Comm: syz.0.17 Not tainted syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:lockdep_unregister_key+0x4d7/0x520 kernel/locking/lockdep.c:6325
Code: 80 00 00 00 75 39 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 f9 57 5c 08 41 f7 c4 00 02 00 00 74 90 fb 84 db 75 8f eb a0 <0f> 0b e9 44 ff ff ff 0f 0b e9 b0 fe ff ff 0f 0b e9 fd fe ff ff e8

RSP: 0018:ffffc900031cf9c0 EFLAGS: 00010002
RAX: 0000000000000000 RBX: ffff88807d655728 RCX: dffffc0000000000
RDX: 0000000000000001 RSI: 0000000000000004 RDI: ffffc900031cf940
RBP: ffffc900031cfa90 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff52000639f28 R12: 0000000000000207
R13: ffff88807d654000 R14: 0000000000000000 R15: 1ffff92000639f3c
FS: 000055557cc67500(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000

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

CR2: 00007ffed284b000 CR3: 000000007595a000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
f2fs_fill_super+0x3ce4/0x7050 fs/f2fs/super.c:4536
mount_bdev+0x28a/0x3c0 fs/super.c:1400
legacy_get_tree+0xe6/0x180 fs/fs_context.c:611
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x247/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3562
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:0x7f1c3f06d0ca

Code: 48 c7 c2 e8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48

RSP: 002b:00007ffed284a138 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffed284a1c0 RCX: 00007f1c3f06d0ca
RDX: 0000200000000000 RSI: 0000200000000280 RDI: 00007ffed284a180
RBP: 0000200000000000 R08: 00007ffed284a1c0 R09: 0000000000000015
R10: 0000000000000015 R11: 0000000000000246 R12: 0000200000000280
R13: 00007ffed284a180 R14: 0000000000005521 R15: 00002000000002c0