[v6.1] WARNING in nilfs_sufile_set_segment_usage

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1cc3fcf63192 Linux 6.1.18
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13c2ca88c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=157296d36f92ea19
dashboard link: https://syzkaller.appspot.com/bug?extid=e9c5f3245bb1654e79eb
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0e4c0d43698b/disk-1cc3fcf6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a4de39d735de/vmlinux-1cc3fcf6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/82bab928f6e3/Image-1cc3fcf6.gz.xz

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

NILFS (loop4): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
WARNING: CPU: 1 PID: 23588 at fs/nilfs2/sufile.c:539 nilfs_sufile_set_segment_usage+0x4a0/0x5a4 fs/nilfs2/sufile.c:539
Modules linked in:
CPU: 1 PID: 23588 Comm: segctord Not tainted 6.1.18-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : nilfs_sufile_set_segment_usage+0x4a0/0x5a4 fs/nilfs2/sufile.c:539
lr : nilfs_sufile_set_segment_usage+0x4a0/0x5a4 fs/nilfs2/sufile.c:539
sp : ffff800020027480
x29: ffff800020027520 x28: dfff800000000000 x27: ffff0000c212606c
x26: ffff0001168b9548 x25: ffff0000c2126060 x24: 0000000000000006
x23: ffff0001168b8000 x22: 0000000000000204 x21: 0000000000000007
x20: ffff8000200274e0 x19: ffff00011493f930 x18: ffff00011493f572
x17: ffff80001572d000 x16: 0000000000000000 x15: 0000000000000000
x14: 0000000000000000 x13: 00000000ffffffef x12: ffff0001168b8000
x11: ff80800009e537bc x10: 0000000000000000 x9 : ffff800009e537bc
x8 : ffff0001168b8000 x7 : ffff800008760b7c x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff800008b3d16c
x2 : 0000000000000001 x1 : 0000000000000004 x0 : 0000000000000000
Call trace:
nilfs_sufile_set_segment_usage+0x4a0/0x5a4 fs/nilfs2/sufile.c:539
nilfs_segctor_update_segusage fs/nilfs2/segment.c:1447 [inline]
nilfs_segctor_do_construct+0x3d4c/0x6604 fs/nilfs2/segment.c:2071
nilfs_segctor_construct+0x110/0x768 fs/nilfs2/segment.c:2379
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline]
nilfs_segctor_thread+0x3e0/0xd88 fs/nilfs2/segment.c:2570
kthread+0x24c/0x2d4 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
irq event stamp: 172
hardirqs last enabled at (171): [<ffff80000897d020>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:242
hardirqs last disabled at (172): [<ffff80001224fb14>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last enabled at (0): [<ffff8000081a7244>] copy_process+0x13c0/0x38d0 kernel/fork.c:2201
softirqs last disabled at (0): [<0000000000000000>] 0x0
---[ end trace 0000000000000000 ]---


---
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: 1cc3fcf63192 Linux 6.1.18
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=166b9724c80000

kernel config: https://syzkaller.appspot.com/x/.config?x=157296d36f92ea19
dashboard link: https://syzkaller.appspot.com/bug?extid=e9c5f3245bb1654e79eb
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1264cc5cc80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=155c512ac80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0e4c0d43698b/disk-1cc3fcf6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a4de39d735de/vmlinux-1cc3fcf6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/82bab928f6e3/Image-1cc3fcf6.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/6f99220eac1e/mount_0.gz

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

NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------
WARNING: CPU: 1 PID: 4324 at fs/nilfs2/sufile.c:539 nilfs_sufile_set_segment_usage+0x4a0/0x5a4 fs/nilfs2/sufile.c:539
Modules linked in:
CPU: 1 PID: 4324 Comm: segctord Not tainted 6.1.18-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : nilfs_sufile_set_segment_usage+0x4a0/0x5a4 fs/nilfs2/sufile.c:539
lr : nilfs_sufile_set_segment_usage+0x4a0/0x5a4 fs/nilfs2/sufile.c:539

sp : ffff80001dcd7480
x29: ffff80001dcd7520 x28: dfff800000000000 x27: ffff0000c4ec806c
x26: ffff0000cd6ae708 x25: ffff0000c4ec8060 x24: 0000000000000006
x23: ffff0000cd6ad1c0 x22: 0000000000000026 x21: 0000000000000007
x20: ffff80001dcd74e0 x19: ffff0000de10a5e8 x18: ffff0000de10a22a
x17: ffff800009e12f94 x16: 0000000000000000 x15: 0000000000000000
x14: 0000000000000000 x13: 00000000ffffffef x12: ffff0000cd6ad1c0

x11: ff80800009e537bc x10: 0000000000000000 x9 : ffff800009e537bc

x8 : ffff0000cd6ad1c0 x7 : ffff800008760b7c x6 : 0000000000000000

x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff800008b3d16c
x2 : 0000000000000001 x1 : 0000000000000004 x0 : 0000000000000000
Call trace:
nilfs_sufile_set_segment_usage+0x4a0/0x5a4 fs/nilfs2/sufile.c:539
nilfs_segctor_update_segusage fs/nilfs2/segment.c:1447 [inline]
nilfs_segctor_do_construct+0x3d4c/0x6604 fs/nilfs2/segment.c:2071
nilfs_segctor_construct+0x110/0x768 fs/nilfs2/segment.c:2379
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline]
nilfs_segctor_thread+0x3e0/0xd88 fs/nilfs2/segment.c:2570
kthread+0x24c/0x2d4 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860

irq event stamp: 196
hardirqs last enabled at (195): [<ffff80000897d020>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:242
hardirqs last disabled at (196): [<ffff80001224fb14>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: bbf9f29bac04 Linux 5.15.101
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17cf31c6c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=353a11a1dbfe7820
dashboard link: https://syzkaller.appspot.com/bug?extid=972ee0057a42ef3c8949

compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=170c7cecc80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10586542c80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/741458b6f24d/disk-bbf9f29b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/46cdc0f15ae5/vmlinux-bbf9f29b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/15bf795c52fa/Image-bbf9f29b.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/3d210ae76955/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+972ee0...@syzkaller.appspotmail.com

NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds
------------[ cut here ]------------

WARNING: CPU: 0 PID: 4054 at fs/nilfs2/sufile.c:539 nilfs_sufile_set_segment_usage+0x4a4/0x5bc fs/nilfs2/sufile.c:539
Modules linked in:
CPU: 0 PID: 4054 Comm: segctord Not tainted 5.15.101-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)

pc : nilfs_sufile_set_segment_usage+0x4a4/0x5bc fs/nilfs2/sufile.c:539
lr : nilfs_sufile_set_segment_usage+0x4a4/0x5bc fs/nilfs2/sufile.c:539
sp : ffff80001a337480
x29: ffff80001a337520 x28: dfff800000000000 x27: ffff0000c7f0906c
x26: ffff0000d9afe520 x25: ffff0000c7f09060 x24: 0000000000000006
x23: ffff0000d9afd040 x22: 000000000000002b x21: 0000000000000007
x20: ffff80001a3374e0 x19: ffff0000df4125e8 x18: 0000000000000000
x17: ff80800009cd76a0 x16: 0000000000000000 x15: ffff800009cd76a0
x14: 00000000ffffffef x13: ffffffffffffffff x12: 0000000000000000
x11: ff80800009d1eb8c x10: 0000000000000000 x9 : ffff800009d1eb8c
x8 : ffff0000d9afd040 x7 : ffff8000086e5ac8 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff800008a763c8

x2 : 0000000000000001 x1 : 0000000000000004 x0 : 0000000000000000
Call trace:

nilfs_sufile_set_segment_usage+0x4a4/0x5bc fs/nilfs2/sufile.c:539
nilfs_segctor_update_segusage fs/nilfs2/segment.c:1447 [inline]
nilfs_segctor_do_construct+0x3f5c/0x6980 fs/nilfs2/segment.c:2071
nilfs_segctor_construct+0x110/0x768 fs/nilfs2/segment.c:2381
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2489 [inline]
nilfs_segctor_thread+0x3c8/0xe98 fs/nilfs2/segment.c:2572
kthread+0x37c/0x45c kernel/kthread.c:319
ret_from_fork+0x10/0x20 <unknown>:870
irq event stamp: 218
hardirqs last enabled at (217): [<ffff8000088d2d9c>] kasan_quarantine_put+0xdc/0x204 mm/kasan/quarantine.c:231
hardirqs last disabled at (218): [<ffff800011a047b0>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (0): [<ffff800008193140>] copy_process+0x12c4/0x3750 kernel/fork.c:2143

softirqs last disabled at (0): [<0000000000000000>] 0x0

---[ end trace 2bcefb9bfa40d0bb ]---

---
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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

[syzbot]

syzbot suspects this issue was fixed by commit:

commit 3907e9cc85ffc49b232dd0b0e8ebe12d3c835a2d
Author: Ryusuke Konishi <konishi...@gmail.com>
Date: Tue Dec 5 08:59:47 2023 +0000

nilfs2: prevent WARNING in nilfs_sufile_set_segment_usage()

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16e5cb71e80000
start commit: 3b29299e5f60 Linux 6.1.22
git tree: linux-6.1.y
kernel config: https://syzkaller.appspot.com/x/.config?x=4a782518325cb082
dashboard link: https://syzkaller.appspot.com/bug?extid=e9c5f3245bb1654e79eb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17e94dcdc80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=159de87dc80000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: nilfs2: prevent WARNING in nilfs_sufile_set_segment_usage()

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

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.