[v6.1] WARNING in nilfs_btree_assign

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7eaef76fbc46 Linux 6.1.20
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=176c4436c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=28c36fe4d02f8c88
dashboard link: https://syzkaller.appspot.com/bug?extid=7d7d35ad4115387264f9
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/610a00ba4375/disk-7eaef76f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/57c1310f9a30/vmlinux-7eaef76f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/81999f717d3b/bzImage-7eaef76f.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 18726 at fs/nilfs2/btree.c:2282 nilfs_btree_assign+0xa9b/0xd00
Modules linked in:
CPU: 0 PID: 18726 Comm: segctord Not tainted 6.1.20-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:nilfs_btree_assign+0xa9b/0xd00 fs/nilfs2/btree.c:2282
Code: 00 0f 85 81 02 00 00 44 89 f0 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 b1 f7 3b fe 4c 8b 7c 24 38 eb a6 e8 a5 f7 3b fe <0f> 0b 41 be fe ff ff ff eb 97 44 89 f1 80 e1 07 80 c1 03 38 c1 0f
RSP: 0018:ffffc90015737580 EFLAGS: 00010293
RAX: ffffffff834e697b RBX: ffff8880853c0ce8 RCX: ffff888028641d40
RDX: 0000000000000000 RSI: 00000000fffffffe RDI: 00000000fffffffe
RBP: ffffc900157376b0 R08: ffffffff834e62d7 R09: ffffed10055be1b4
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff88801e3f6180 R14: 00000000fffffffe R15: 1ffff92002ae6ec0
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020034030 CR3: 0000000037a5a000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
nilfs_bmap_assign+0x87/0x160 fs/nilfs2/bmap.c:382
nilfs_segctor_update_payload_blocknr fs/nilfs2/segment.c:1595 [inline]
nilfs_segctor_assign fs/nilfs2/segment.c:1629 [inline]
nilfs_segctor_do_construct+0x39c1/0x6f00 fs/nilfs2/segment.c:2056
nilfs_segctor_construct+0x145/0x8c0 fs/nilfs2/segment.c:2379
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline]
nilfs_segctor_thread+0x536/0x1130 fs/nilfs2/segment.c:2570
kthread+0x268/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 7eaef76fbc46 Linux 6.1.20
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=17840466c80000

kernel config: https://syzkaller.appspot.com/x/.config?x=28c36fe4d02f8c88
dashboard link: https://syzkaller.appspot.com/bug?extid=7d7d35ad4115387264f9
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16bedeeec80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/610a00ba4375/disk-7eaef76f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/57c1310f9a30/vmlinux-7eaef76f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/81999f717d3b/bzImage-7eaef76f.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/9d8ebc996226/mount_0.gz

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

------------[ cut here ]------------

WARNING: CPU: 0 PID: 5017 at fs/nilfs2/btree.c:2282 nilfs_btree_assign+0xa9b/0xd00
Modules linked in:
CPU: 0 PID: 5017 Comm: segctord Not tainted 6.1.20-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:nilfs_btree_assign+0xa9b/0xd00 fs/nilfs2/btree.c:2282
Code: 00 0f 85 81 02 00 00 44 89 f0 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 b1 f7 3b fe 4c 8b 7c 24 38 eb a6 e8 a5 f7 3b fe <0f> 0b 41 be fe ff ff ff eb 97 44 89 f1 80 e1 07 80 c1 03 38 c1 0f

RSP: 0018:ffffc9000ba4f580 EFLAGS: 00010293
RAX: ffffffff834e697b RBX: ffff88806984ed00 RCX: ffff8880202e3a80

RDX: 0000000000000000 RSI: 00000000fffffffe RDI: 00000000fffffffe

RBP: ffffc9000ba4f6b0 R08: ffffffff834e62d7 R09: ffffed100e4fee3b

R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000

R13: ffff88806669f800 R14: 00000000fffffffe R15: 1ffff92001749ec0

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

CR2: 00007fbbe302b000 CR3: 0000000078ef2000 CR4: 00000000003506f0

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: fa74641fb6b9 Linux 6.1.29
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13a7def9280000
kernel config: https://syzkaller.appspot.com/x/.config?x=fac5c36c2b16009f

dashboard link: https://syzkaller.appspot.com/bug?extid=7d7d35ad4115387264f9
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17589e91280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1139f37e280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3e78f005d7f8/disk-fa74641f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6527fcf66401/vmlinux-fa74641f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c5e0d5f8b434/bzImage-fa74641f.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/d46d266ebfbf/mount_0.gz

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

------------[ cut here ]------------

WARNING: CPU: 0 PID: 7345 at fs/nilfs2/btree.c:2282 nilfs_btree_assign+0xa9b/0xd00
Modules linked in:
CPU: 0 PID: 7345 Comm: segctord Not tainted 6.1.29-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023

RIP: 0010:nilfs_btree_assign+0xa9b/0xd00 fs/nilfs2/btree.c:2282

Code: 00 0f 85 81 02 00 00 44 89 f0 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 91 6c 40 fe 4c 8b 7c 24 38 eb a6 e8 85 6c 40 fe <0f> 0b 41 be fe ff ff ff eb 97 44 89 f1 80 e1 07 80 c1 03 38 c1 0f
RSP: 0018:ffffc9000e637580 EFLAGS: 00010293
RAX: ffffffff8349584b RBX: ffff8880725d8018 RCX: ffff888027d81dc0

RDX: 0000000000000000 RSI: 00000000fffffffe RDI: 00000000fffffffe

RBP: ffffc9000e6376b0 R08: ffffffff834951a7 R09: ffffed100d8b3f40

R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000

R13: ffff888077124b00 R14: 00000000fffffffe R15: 1ffff92001cc6ec0

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

CR2: 00007f0f48a6f000 CR3: 000000001b977000 CR4: 00000000003506f0

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

nilfs_bmap_assign+0x87/0x160 fs/nilfs2/bmap.c:390
nilfs_segctor_update_payload_blocknr fs/nilfs2/segment.c:1615 [inline]
nilfs_segctor_assign fs/nilfs2/segment.c:1649 [inline]
nilfs_segctor_do_construct+0x374c/0x6cc0 fs/nilfs2/segment.c:2079
nilfs_segctor_construct+0x145/0x8c0 fs/nilfs2/segment.c:2402
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2510 [inline]
nilfs_segctor_thread+0x536/0x1130 fs/nilfs2/segment.c:2593
kthread+0x26e/0x300 kernel/kthread.c:376

ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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.