[v5.15] WARNING in nilfs_dat_commit_end

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8020ae3c051d Linux 5.15.103
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1080f131c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d4215fb4040f8f8d
dashboard link: https://syzkaller.appspot.com/bug?extid=f95e0d2bc2dc67bc22bb
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/857e17de0f0a/disk-8020ae3c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9efc49fcd441/vmlinux-8020ae3c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f14c38b6bfa7/bzImage-8020ae3c.xz

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

NILFS (loop3): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3937 at fs/nilfs2/dat.c:193 nilfs_dat_commit_end+0x59c/0x6a0
Modules linked in:
CPU: 1 PID: 3937 Comm: segctord Not tainted 5.15.103-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:nilfs_dat_commit_end+0x59c/0x6a0 fs/nilfs2/dat.c:193
Code: 48 89 ee 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f 5d e9 d8 81 03 00 e8 13 b3 57 fe e8 3e c4 d7 fd e9 d8 fc ff ff e8 04 b3 57 fe <0f> 0b e9 39 fc ff ff e8 f8 b2 57 fe e8 23 c4 d7 fd 43 80 7c 35 00
RSP: 0018:ffffc9000538f2c8 EFLAGS: 00010293
RAX: ffffffff8328c5cc RBX: ffff888084a9b1a0 RCX: ffff88807529d700
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0001000000000002
RBP: 0000000000000003 R08: ffffffff8328c1fe R09: ffffed100f3e9c9b
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888075010180
R13: 1ffff92000a71e7b R14: 0001000000000002 R15: ffff88807529edb8
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005647bbe55e50 CR3: 000000007ced6000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
nilfs_dat_commit_update+0x25/0x40 fs/nilfs2/dat.c:243
nilfs_direct_propagate+0x23c/0x3b0 fs/nilfs2/direct.c:277
nilfs_bmap_propagate+0x6d/0x120 fs/nilfs2/bmap.c:337
nilfs_collect_file_data+0x49/0xc0 fs/nilfs2/segment.c:568
nilfs_segctor_apply_buffers+0x180/0x330 fs/nilfs2/segment.c:1018
nilfs_segctor_scan_file+0x82d/0xad0 fs/nilfs2/segment.c:1067
nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1197 [inline]
nilfs_segctor_collect fs/nilfs2/segment.c:1503 [inline]
nilfs_segctor_do_construct+0x1e63/0x7410 fs/nilfs2/segment.c:2045
nilfs_segctor_construct+0x145/0x8c0 fs/nilfs2/segment.c:2381
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2489 [inline]
nilfs_segctor_thread+0x54c/0x1140 fs/nilfs2/segment.c:2572
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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]

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=11ee14a1c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=28c36fe4d02f8c88
dashboard link: https://syzkaller.appspot.com/bug?extid=360baff8facad197fe86

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+360baf...@syzkaller.appspotmail.com

NILFS (loop5): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
WARNING: CPU: 1 PID: 20827 at fs/nilfs2/dat.c:193 nilfs_dat_commit_end+0x59c/0x6a0
Modules linked in:
CPU: 1 PID: 20827 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_dat_commit_end+0x59c/0x6a0 fs/nilfs2/dat.c:193

Code: 48 89 ee 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f 5d e9 08 80 03 00 e8 b3 3b 3b fe e8 ee 6a b1 fd e9 d8 fc ff ff e8 a4 3b 3b fe <0f> 0b e9 39 fc ff ff e8 98 3b 3b fe e8 d3 6a b1 fd 43 80 7c 35 00
RSP: 0018:ffffc9000b39f288 EFLAGS: 00010293
RAX: ffffffff834f257c RBX: ffff8880780be1a0 RCX: ffff88801f32d7c0

RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0001000000000002

RBP: 0000000000000003 R08: ffffffff834f21ae R09: ffffed100f48a51b
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807aad1180
R13: 1ffff92001673e73 R14: 0001000000000002 R15: ffff88801f32eea0
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000

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

CR2: 00007efd1a4cc690 CR3: 0000000080287000 CR4: 00000000003506e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
nilfs_dat_commit_update+0x25/0x40 fs/nilfs2/dat.c:243
nilfs_direct_propagate+0x23c/0x3b0 fs/nilfs2/direct.c:277
nilfs_bmap_propagate+0x6d/0x120 fs/nilfs2/bmap.c:337
nilfs_collect_file_data+0x49/0xc0 fs/nilfs2/segment.c:568
nilfs_segctor_apply_buffers+0x180/0x330 fs/nilfs2/segment.c:1018
nilfs_segctor_scan_file+0x82d/0xad0 fs/nilfs2/segment.c:1067
nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1197 [inline]
nilfs_segctor_collect fs/nilfs2/segment.c:1503 [inline]

nilfs_segctor_do_construct+0x1d87/0x6f00 fs/nilfs2/segment.c:2045
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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 115472395b0a Linux 5.15.104
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=157739f9c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5592cc4916e1c2f

dashboard link: https://syzkaller.appspot.com/bug?extid=f95e0d2bc2dc67bc22bb
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=16f4857ac80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f6da5ac80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6c2c0744c7e0/disk-11547239.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7ea4c5ecca4f/vmlinux-11547239.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9a231dbcf423/bzImage-11547239.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/ed234f25139f/mount_0.gz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 3586 at fs/nilfs2/dat.c:193 nilfs_dat_commit_end+0x59c/0x6a0
Modules linked in:
CPU: 1 PID: 3586 Comm: segctord Not tainted 5.15.104-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:nilfs_dat_commit_end+0x59c/0x6a0 fs/nilfs2/dat.c:193

Code: 48 89 ee 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f 5d e9 88 7d 03 00 e8 e3 26 5c fe e8 de f5 dc fd e9 d8 fc ff ff e8 d4 26 5c fe <0f> 0b e9 39 fc ff ff e8 c8 26 5c fe e8 c3 f5 dc fd 43 80 7c 35 00
RSP: 0018:ffffc90002c4f2c8 EFLAGS: 00010293
RAX: ffffffff8323910c RBX: ffff88801e9611a0 RCX: ffff888019279d00
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000302
RBP: 0000000000000003 R08: ffffffff83238d3e R09: ffffed100332de9b
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807c9dbaa0
R13: 1ffff92000589e7b R14: 0000000000000302 R15: ffff88801927b3b8

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

CR2: 00005586536c1000 CR3: 000000002378a000 CR4: 00000000003506e0

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: e3a87a10f259 Linux 6.1.21
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1113ec39c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b49b0405a60858ed

dashboard link: https://syzkaller.appspot.com/bug?extid=360baff8facad197fe86
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=17af06b1c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=103019f9c80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed3d1f3e75e6/disk-e3a87a10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6d8e44c8c75c/vmlinux-e3a87a10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cebe803ea4fa/bzImage-e3a87a10.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3175a9412734/mount_0.gz

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

NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3632 at fs/nilfs2/dat.c:193 nilfs_dat_commit_end+0x59c/0x6a0
Modules linked in:
CPU: 0 PID: 3632 Comm: segctord Not tainted 6.1.21-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:nilfs_dat_commit_end+0x59c/0x6a0 fs/nilfs2/dat.c:193

Code: 48 89 ee 48 83 c4 38 5b 41 5c 41 5d 41 5e 41 5f 5d e9 d8 7b 03 00 e8 63 0d 40 fe e8 ce 12 b7 fd e9 d8 fc ff ff e8 54 0d 40 fe <0f> 0b e9 39 fc ff ff e8 48 0d 40 fe e8 b3 12 b7 fd 43 80 7c 35 00
RSP: 0018:ffffc90003d3f288 EFLAGS: 00010293
RAX: ffffffff83497a8c RBX: ffff888026c9d1a0 RCX: ffff88801f9a8000
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000302
RBP: 0000000000000003 R08: ffffffff834976be R09: ffffed100433b21b
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807bf58aa0
R13: 1ffff920007a7e73 R14: 0000000000000302 R15: ffff88801f9a96e0
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000

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

CR2: 000055e52504ee48 CR3: 000000001da7d000 CR4: 00000000003506f0

[syzbot]

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

commit 28a65b49eb53e172d23567005465019658bfdb4d
git tree: upstream
Author: Ryusuke Konishi <konishi...@gmail.com>
Date: Thu Apr 27 01:15:26 2023 +0000

nilfs2: do not write dirty data after degenerating to read-only

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15e369dba80000

kernel config: https://syzkaller.appspot.com/x/.config?x=b49b0405a60858ed
dashboard link: https://syzkaller.appspot.com/bug?extid=360baff8facad197fe86

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17af06b1c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=103019f9c80000

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

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

[syzbot]

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

commit 28a65b49eb53e172d23567005465019658bfdb4d
git tree: upstream
Author: Ryusuke Konishi <konishi...@gmail.com>
Date: Thu Apr 27 01:15:26 2023 +0000

nilfs2: do not write dirty data after degenerating to read-only

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14f9cc5fa80000

kernel config: https://syzkaller.appspot.com/x/.config?x=f5592cc4916e1c2f
dashboard link: https://syzkaller.appspot.com/bug?extid=f95e0d2bc2dc67bc22bb

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16f4857ac80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10f6da5ac80000