Skip to contentSkip to conversation

Status of running xfstests for NILFS2

DISCUSSION Viacheslav Dubeyko 3 participants 11 messages Nov 14, 2025 – Dec 25, 2025 NILFS2 filesystem

lore
Share & tools
lore
#0 lore raw

Hi Ryusuke,

I did run the xfstests suite for NILFS2. As far as I can see, there are 156 failed tests and I needed to exclude 2 tests from running.

sudo ./check -g auto -E ./my_exclude.txt
FSTYP -- nilfs2
PLATFORM -- Linux/x86_64 hfsplus-testing-0001 6.18.0-rc3+ #93 SMP
PREEMPT_DYNAMIC Wed Nov 12 14:37:49 PST 2025
MKFS_OPTIONS -- /dev/loop51
MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch

<skipped>

Failures: generic/003 generic/040 generic/041 generic/068 generic/074 generic/075 generic/078 generic/080 generic/086 generic/092 generic/097 generic/099 generic/100 generic/103 generic/105 generic/109 generic/112 generic/117 generic/121 generic/122 generic/124 generic/127 generic/129 generic/131 generic/136 generic/177 generic/182 generic/192 generic/215 generic/221 generic/237 generic/241 generic/245 generic/246 generic/247 generic/248 generic/249 generic/251 generic/255 generic/257 generic/258 generic/260 generic/285 generic/286 generic/307 generic/309 generic/310 generic/313 generic/316 generic/318 generic/319 generic/322 generic/337 generic/348 generic/360 generic/363 generic/365 generic/375 generic/376 generic/377 generic/394 generic/403 generic/404 generic/408 generic/409 generic/410 generic/411 generic/420 generic/425 generic/428 generic/430 generic/431 generic/432 generic/433 generic/436 generic/437 generic/438 generic/439 generic/443 generic/444 generic/445 generic/448 generic/469 generic/471 generic/478 generic/483 generic/484 generic/485 generic/486 generic/489 generic/490 generic/503 generic/504 generic/510 generic/512 generic/516 generic/519 generic/523 generic/529 generic/533 generic/535 generic/537 generic/539 generic/547 generic/553 generic/555 generic/563 generic/565 generic/567 generic/568 generic/571 generic/585 generic/589 generic/590 generic/607 generic/610 generic/611 generic/614 generic/616 generic/618 generic/629 generic/631 generic/632 generic/634 generic/637 generic/638 generic/639 generic/640 generic/650 generic/676 generic/690 generic/695 generic/697 generic/704 generic/706 generic/712 generic/713 generic/715 generic/718 generic/719 generic/723 generic/724 generic/725 generic/728 generic/732 generic/736 generic/738 generic/741 generic/742 generic/749 generic/754 generic/758 generic/759 generic/763 generic/764 generic/771
Failed 156 of 767 tests

I needed to exclude generic/740 and generic/753. I am not completely sure what is wrong with generic/740 (it could be glitch on my side). But generic/753 fills the system log with bunch of errors:

2025-11-12T18:36:24.171533-08:00 hfsplus-testing-0001 root: run xfstest
generic/753
2025-11-12T18:36:24.175432-08:00 hfsplus-testing-0001 kernel: run fstests
generic/753 at 2025-11-12 18:36:24
2025-11-12T18:36:24.243745-08:00 hfsplus-testing-0001 systemd[1]: Started
fstests-generic-753.scope - /usr/bin/bash -c "test -w
 /proc/self/oom_score_adj && echo 250 > /proc/self/oom_score_adj; exec
./tests/generic/753".
2025-11-12T18:36:26.068288-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0):
segctord starting. Construction interval = 5 second
s, CP frequency < 30 seconds
2025-11-12T18:36:26.082067-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
start
2025-11-12T18:36:26.082949-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
pause (clean check)
2025-11-12T18:36:28.111323-08:00 hfsplus-testing-0001 kernel: Buffer I/O error
on dev dm-0, logical block 2621424, async page r
ead
2025-11-12T18:36:28.203453-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=18209, block-c
ount=223) in segment 8
2025-11-12T18:36:28.203467-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=18432, block-c
ount=2048) in segment 9
2025-11-12T18:36:28.203468-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=20480, block-c
ount=1369) in segment 10
2025-11-12T18:36:28.221444-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=18432, block-c
ount=2048) in segment 9
2025-11-12T18:36:28.221463-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=24576, block-c
ount=1592) in segment 12
2025-11-12T18:36:28.248445-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=18432, block-c
ount=2048) in segment 9
2025-11-12T18:36:28.248458-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=28672, block-c
ount=2048) in segment 14
2025-11-12T18:36:28.248459-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=30720, block-c
ount=416) in segment 15
2025-11-12T18:36:28.274445-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=18432, block-c
ount=2048) in segment 9
2025-11-12T18:36:28.274459-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=34816, block-c
ount=2048) in segment 17
2025-11-12T18:36:28.274460-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=36864, block-c
ount=417) in segment 18
2025-11-12T18:36:28.308978-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
shutdown
2025-11-12T18:36:28.322418-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=18432, block-c
ount=2048) in segment 9
2025-11-12T18:36:28.322433-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=40960, block-c
ount=2048) in segment 20
2025-11-12T18:36:28.322434-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=43008, block-c
ount=418) in segment 21
2025-11-12T18:36:28.323970-08:00 hfsplus-testing-0001 systemd[1]: mnt-
scratch.mount: Deactivated successfully.
2025-11-12T18:36:28.398412-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=18432, block-c
ount=2048) in segment 9
2025-11-12T18:36:28.398428-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O
error writing log (start-blocknr=47104, block-c
ount=2048) in segment 23
2025-11-12T18:36:28.398430-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O

error writing log (start-blocknr=49152, block-c
ount=418) in segment 24

I need to double check but likewise error happens not only for generic/753 test- case. As far as I can see, other test-cases also triggered such issue. But namely generic/753 hangs infinitely with such error messages.

I believe it makes sense to account all of these issues in some tracking system before starting to fix it. Are you using any tracking system for NILFS2 issues? Frankly speaking, I am using github's tracking system for HFS/HFS+ issues [1]. It's simple enough but I don't need in more complex system for this right now. So, what do you think about some bug tracking system for NILFS2?

As far as I can see, syzbot still reports about 5 issues for NILFS2 [2]. So, it makes sense to account these issues too.

I am working on Kunit-based unit-tests for CephFS, HFS/HFS+, SSDFS. So, I believe that NILFS2 could benefit also from having likewise unit-tests. How do you feel about it?

I am going to attend LPC 2025 in Tokyo (December 11 - 13, 2025). And I am planning to have 2 free days before conference start. Are you planning to attend LPC 2025?

Thanks,
Slava.

[1] https://github.com/hfs-linux-kernel/hfs-linux-kernel/issues
[2]
https://lore.kernel.org/linux-nilfs/[email protected]/T/#u

maintainer
#1 lore raw

Hi Viacheslav,

Quoted 66 lines · Viacheslav Dubeyko

Hi Ryusuke,

I did run the xfstests suite for NILFS2. As far as I can see, there are 156 failed tests and I needed to exclude 2 tests from running.

sudo ./check -g auto -E ./my_exclude.txt
FSTYP -- nilfs2
PLATFORM -- Linux/x86_64 hfsplus-testing-0001 6.18.0-rc3+ #93 SMP
PREEMPT_DYNAMIC Wed Nov 12 14:37:49 PST 2025
MKFS_OPTIONS -- /dev/loop51
MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch

<skipped>

Failures: generic/003 generic/040 generic/041 generic/068 generic/074 generic/075 generic/078 generic/080 generic/086 generic/092 generic/097 generic/099 generic/100 generic/103 generic/105 generic/109 generic/112 generic/117 generic/121 generic/122 generic/124 generic/127 generic/129 generic/131 generic/136 generic/177 generic/182 generic/192 generic/215 generic/221 generic/237 generic/241 generic/245 generic/246 generic/247 generic/248 generic/249 generic/251 generic/255 generic/257 generic/258 generic/260 generic/285 generic/286 generic/307 generic/309 generic/310 generic/313 generic/316 generic/318 generic/319 generic/322 generic/337 generic/348 generic/360 generic/363 generic/365 generic/375 generic/376 generic/377 generic/394 generic/403 generic/404 generic/408 generic/409 generic/410 generic/411 generic/420 generic/425 generic/428 generic/430 generic/431 generic/432 generic/433 generic/436 generic/437 generic/438 generic/439 generic/443 generic/444 generic/445 generic/448 generic/469 generic/471 generic/478 generic/483 generic/484 generic/485 generic/486 generic/489 generic/490 generic/503 generic/504 generic/510 generic/512 generic/516 generic/519 generic/523 generic/529 generic/533 generic/535 generic/537 generic/539 generic/547 generic/553 generic/555 generic/563 generic/565 generic/567 generic/568 generic/571 generic/585 generic/589 generic/590 generic/607 generic/610 generic/611 generic/614 generic/616 generic/618 generic/629 generic/631 generic/632 generic/634 generic/637 generic/638 generic/639 generic/640 generic/650 generic/676 generic/690 generic/695 generic/697 generic/704 generic/706 generic/712 generic/713 generic/715 generic/718 generic/719 generic/723 generic/724 generic/725 generic/728 generic/732 generic/736 generic/738 generic/741 generic/742 generic/749 generic/754 generic/758 generic/759 generic/763 generic/764 generic/771
Failed 156 of 767 tests

I needed to exclude generic/740 and generic/753. I am not completely sure what is wrong with generic/740 (it could be glitch on my side). But generic/753 fills the system log with bunch of errors:

2025-11-12T18:36:24.171533-08:00 hfsplus-testing-0001 root: run xfstest
generic/753
2025-11-12T18:36:24.175432-08:00 hfsplus-testing-0001 kernel: run fstests
generic/753 at 2025-11-12 18:36:24
2025-11-12T18:36:24.243745-08:00 hfsplus-testing-0001 systemd[1]: Started
fstests-generic-753.scope - /usr/bin/bash -c "test -w
 /proc/self/oom_score_adj && echo 250 > /proc/self/oom_score_adj; exec
./tests/generic/753".
2025-11-12T18:36:26.068288-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0):
segctord starting. Construction interval = 5 second
s, CP frequency < 30 seconds
2025-11-12T18:36:26.082067-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
start
2025-11-12T18:36:26.082949-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
pause (clean check)
2025-11-12T18:36:28.111323-08:00 hfsplus-testing-0001 kernel: Buffer I/O error

on dev dm-0, logical block 2621424, async page r
ead

...

Quoted 7 lines
2025-11-12T18:36:28.398430-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O

error writing log (start-blocknr=49152, block-c
ount=418) in segment 24

I need to double check but likewise error happens not only for generic/753 test- case. As far as I can see, other test-cases also triggered such issue. But namely generic/753 hangs infinitely with such error messages.

Okay, I'll take a look at xfstests/753 and related tests. To be honest, I've been busy lately and haven't had much time, but I hope to have some time after Tuesday.

Quoted 5 lines

I believe it makes sense to account all of these issues in some tracking system before starting to fix it. Are you using any tracking system for NILFS2 issues? Frankly speaking, I am using github's tracking system for HFS/HFS+ issues [1]. It's simple enough but I don't need in more complex system for this right now. So, what do you think about some bug tracking system for NILFS2?

We don't have a central BTS that we operate. We did have one during development, but it wasn't open and is no longer usable. So we either use a mailing list or syzbot, and although I don't particularly want or use it, nilfs-utils' github plays a role in that regard.

As for managing issues raised by xfstests, as you say, I agree that a proper BTS is needed.
However, something that is heavily web-dependent like github doesn't work well with mailing lists, so I'm honestly not sure if it's a good solution for this project, apart from github-based development projects.

In this regard, I think syzbot is good, because email exchanges naturally become a response history and are easily shared with the mailing list.
Unfortunately, it doesn't cover the entire issue tracking.

If you're going to use github for issue tracking, it would be better if it could be set up to be highly compatible with mailing lists. What do you think?

Personally, I'd like to see a better issue tracking system that can bridge with email-driven workflows, flexibly connect with AI, and support OSS activity, but I don't know of anything other than GitHub that I think would be suitable.

Quoted 2 lines

As far as I can see, syzbot still reports about 5 issues for NILFS2 [2]. So, it makes sense to account these issues too.

I think it's fine to use it solely for issue management purposes, as long as it doesn't result in double management. Therefore, I think we should make sure to always jump to syzbot from GitHub, etc., as an index, and make good use of syzbot's workflow as is.

Quoted 3 lines

I am working on Kunit-based unit-tests for CephFS, HFS/HFS+, SSDFS. So, I believe that NILFS2 could benefit also from having likewise unit-tests. How do you feel about it?

As for using Kunit, I'm not sure how to effectively extract unit tests while avoiding I/O and page caching.
Rather, what parts of HFS/HFS+ do you extract and write tests for?

Quoted 4 lines

I am going to attend LPC 2025 in Tokyo (December 11 - 13, 2025). And I am planning to have 2 free days before conference start. Are you planning to attend LPC 2025?

I'm not participating. But welcome to Japan ;)

It might have been a good opportunity to meet you. However, since I'm not a native speaker, I honestly find email communication more efficient than face-to-face communication.
Also, while it's not a health issue, personal circumstances have been making it difficult for me to move around freely recently.

Well, it's not like I can't come at all, so if you still want to have a face-to-face discussion for the future, please let me know via private message.

Thanks,
Ryusuke Konishi

Quoted 6 lines

Thanks,
Slava.

[1] https://github.com/hfs-linux-kernel/hfs-linux-kernel/issues
[2]
https://lore.kernel.org/linux-nilfs/[email protected]/T/#u

#2 lore raw

Hi Ryusuke,

Quoted 74 lines · Ryusuke Konishi

Hi Viacheslav,

Quoted 66 lines · Viacheslav Dubeyko

Hi Ryusuke,

I did run the xfstests suite for NILFS2. As far as I can see, there are 156 failed tests and I needed to exclude 2 tests from running.

sudo ./check -g auto -E ./my_exclude.txt
FSTYP -- nilfs2
PLATFORM -- Linux/x86_64 hfsplus-testing-0001 6.18.0-rc3+ #93 SMP
PREEMPT_DYNAMIC Wed Nov 12 14:37:49 PST 2025
MKFS_OPTIONS -- /dev/loop51
MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch

<skipped>

Failures: generic/003 generic/040 generic/041 generic/068 generic/074 generic/075 generic/078 generic/080 generic/086 generic/092 generic/097 generic/099 generic/100 generic/103 generic/105 generic/109 generic/112 generic/117 generic/121 generic/122 generic/124 generic/127 generic/129 generic/131 generic/136 generic/177 generic/182 generic/192 generic/215 generic/221 generic/237 generic/241 generic/245 generic/246 generic/247 generic/248 generic/249 generic/251 generic/255 generic/257 generic/258 generic/260 generic/285 generic/286 generic/307 generic/309 generic/310 generic/313 generic/316 generic/318 generic/319 generic/322 generic/337 generic/348 generic/360 generic/363 generic/365 generic/375 generic/376 generic/377 generic/394 generic/403 generic/404 generic/408 generic/409 generic/410 generic/411 generic/420 generic/425 generic/428 generic/430 generic/431 generic/432 generic/433 generic/436 generic/437 generic/438 generic/439 generic/443 generic/444 generic/445 generic/448 generic/469 generic/471 generic/478 generic/483 generic/484 generic/485 generic/486 generic/489 generic/490 generic/503 generic/504 generic/510 generic/512 generic/516 generic/519 generic/523 generic/529 generic/533 generic/535 generic/537 generic/539 generic/547 generic/553 generic/555 generic/563 generic/565 generic/567 generic/568 generic/571 generic/585 generic/589 generic/590 generic/607 generic/610 generic/611 generic/614 generic/616 generic/618 generic/629 generic/631 generic/632 generic/634 generic/637 generic/638 generic/639 generic/640 generic/650 generic/676 generic/690 generic/695 generic/697 generic/704 generic/706 generic/712 generic/713 generic/715 generic/718 generic/719 generic/723 generic/724 generic/725 generic/728 generic/732 generic/736 generic/738 generic/741 generic/742 generic/749 generic/754 generic/758 generic/759 generic/763 generic/764 generic/771
Failed 156 of 767 tests

I needed to exclude generic/740 and generic/753. I am not completely sure what is wrong with generic/740 (it could be glitch on my side). But generic/753 fills the system log with bunch of errors:

2025-11-12T18:36:24.171533-08:00 hfsplus-testing-0001 root: run xfstest
generic/753
2025-11-12T18:36:24.175432-08:00 hfsplus-testing-0001 kernel: run fstests
generic/753 at 2025-11-12 18:36:24
2025-11-12T18:36:24.243745-08:00 hfsplus-testing-0001 systemd[1]: Started
fstests-generic-753.scope - /usr/bin/bash -c "test -w
 /proc/self/oom_score_adj && echo 250 > /proc/self/oom_score_adj; exec
./tests/generic/753".
2025-11-12T18:36:26.068288-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0):
segctord starting. Construction interval = 5 second
s, CP frequency < 30 seconds
2025-11-12T18:36:26.082067-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
start
2025-11-12T18:36:26.082949-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
pause (clean check)
2025-11-12T18:36:28.111323-08:00 hfsplus-testing-0001 kernel: Buffer I/O error

on dev dm-0, logical block 2621424, async page r
ead

...

Quoted 4 lines
2025-11-12T18:36:28.398430-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O

error writing log (start-blocknr=49152, block-c
ount=418) in segment 24

Quoted 8 lines
Quoted 3 lines

I need to double check but likewise error happens not only for generic/753 test- case. As far as I can see, other test-cases also triggered such issue. But namely generic/753 hangs infinitely with such error messages.

Okay, I'll take a look at xfstests/753 and related tests. To be honest, I've been busy lately and haven't had much time, but I hope to have some time after Tuesday.

It's OK. We are not in a hurry. And it's a lot of tests are failing right now.

Quoted 19 lines
Quoted 5 lines

I believe it makes sense to account all of these issues in some tracking system before starting to fix it. Are you using any tracking system for NILFS2 issues? Frankly speaking, I am using github's tracking system for HFS/HFS+ issues [1]. It's simple enough but I don't need in more complex system for this right now. So, what do you think about some bug tracking system for NILFS2?

We don't have a central BTS that we operate. We did have one during development, but it wasn't open and is no longer usable. So we either use a mailing list or syzbot, and although I don't particularly want or use it, nilfs-utils' github plays a role in that regard.

As for managing issues raised by xfstests, as you say, I agree that a proper BTS is needed.
However, something that is heavily web-dependent like github doesn't work well with mailing lists, so I'm honestly not sure if it's a good solution for this project, apart from github-based development projects.

Quoted 9 lines

In this regard, I think syzbot is good, because email exchanges naturally become a response history and are easily shared with the mailing list.
Unfortunately, it doesn't cover the entire issue tracking.

If you're going to use github for issue tracking, it would be better if it could be set up to be highly compatible with mailing lists. What do you think?

I like your suggestion. But what particular BTS candidate do you have in mind?

Quoted 5 lines

Personally, I'd like to see a better issue tracking system that can bridge with email-driven workflows, flexibly connect with AI, and support OSS activity, but I don't know of anything other than GitHub that I think would be suitable.

So, this is my worry that we could not find good and free BTS. And, finally, we will need to use anything not very good but accessible right now. :)

Quoted 9 lines
Quoted 2 lines

As far as I can see, syzbot still reports about 5 issues for NILFS2 [2]. So, it makes sense to account these issues too.

I think it's fine to use it solely for issue management purposes, as long as it doesn't result in double management. Therefore, I think we should make sure to always jump to syzbot from GitHub, etc., as an index, and make good use of syzbot's workflow as is.

I am simply thinking to have some tracking system that can account all NILFS2 issues. The syzbot has its own tracking system. But, from my point of view, it makes sense to account syzbot issues like sub-class of issues.

Quoted 8 lines
Quoted 3 lines

I am working on Kunit-based unit-tests for CephFS, HFS/HFS+, SSDFS. So, I believe that NILFS2 could benefit also from having likewise unit-tests. How do you feel about it?

As for using Kunit, I'm not sure how to effectively extract unit tests while avoiding I/O and page caching.
Rather, what parts of HFS/HFS+ do you extract and write tests for?

Usually, unit-tests check correctness of functions' logic in isolated environment. So, unit-test logic can create local fake object(s) that will not involve complex logic of the rest kernel functionality. Most frequently, file system can implement multiple internal primitives (like bitmap, b-tree, etc). And unit-tests check this internal functionality likewise it can be called by other file system's part or by VFS. I've found that unit-testing is very useful frequently. It cannot detect all bugs but it can find simple but not always trivial issues in file system's code.

Quoted 7 lines
Quoted 4 lines

I am going to attend LPC 2025 in Tokyo (December 11 - 13, 2025). And I am planning to have 2 free days before conference start. Are you planning to attend LPC 2025?

I'm not participating. But welcome to Japan ;)

Thanks. :) I hope I will not be lost there. :)

Quoted 10 lines

It might have been a good opportunity to meet you. However, since I'm not a native speaker, I honestly find email communication more efficient than face-to-face communication.
Also, while it's not a health issue, personal circumstances have been making it difficult for me to move around freely recently.

Well, it's not like I can't come at all, so if you still want to have a face-to-face discussion for the future, please let me know via private message.

OK. I see. No problem. :)

Thanks,
Slava.

maintainer
#3 lore raw
Quoted 113 lines · Viacheslav Dubeyko

Hi Ryusuke,

Quoted 74 lines · Ryusuke Konishi

Hi Viacheslav,

Quoted 66 lines · Viacheslav Dubeyko

Hi Ryusuke,

I did run the xfstests suite for NILFS2. As far as I can see, there are 156 failed tests and I needed to exclude 2 tests from running.

sudo ./check -g auto -E ./my_exclude.txt
FSTYP -- nilfs2
PLATFORM -- Linux/x86_64 hfsplus-testing-0001 6.18.0-rc3+ #93 SMP
PREEMPT_DYNAMIC Wed Nov 12 14:37:49 PST 2025
MKFS_OPTIONS -- /dev/loop51
MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch

<skipped>

Failures: generic/003 generic/040 generic/041 generic/068 generic/074 generic/075 generic/078 generic/080 generic/086 generic/092 generic/097 generic/099 generic/100 generic/103 generic/105 generic/109 generic/112 generic/117 generic/121 generic/122 generic/124 generic/127 generic/129 generic/131 generic/136 generic/177 generic/182 generic/192 generic/215 generic/221 generic/237 generic/241 generic/245 generic/246 generic/247 generic/248 generic/249 generic/251 generic/255 generic/257 generic/258 generic/260 generic/285 generic/286 generic/307 generic/309 generic/310 generic/313 generic/316 generic/318 generic/319 generic/322 generic/337 generic/348 generic/360 generic/363 generic/365 generic/375 generic/376 generic/377 generic/394 generic/403 generic/404 generic/408 generic/409 generic/410 generic/411 generic/420 generic/425 generic/428 generic/430 generic/431 generic/432 generic/433 generic/436 generic/437 generic/438 generic/439 generic/443 generic/444 generic/445 generic/448 generic/469 generic/471 generic/478 generic/483 generic/484 generic/485 generic/486 generic/489 generic/490 generic/503 generic/504 generic/510 generic/512 generic/516 generic/519 generic/523 generic/529 generic/533 generic/535 generic/537 generic/539 generic/547 generic/553 generic/555 generic/563 generic/565 generic/567 generic/568 generic/571 generic/585 generic/589 generic/590 generic/607 generic/610 generic/611 generic/614 generic/616 generic/618 generic/629 generic/631 generic/632 generic/634 generic/637 generic/638 generic/639 generic/640 generic/650 generic/676 generic/690 generic/695 generic/697 generic/704 generic/706 generic/712 generic/713 generic/715 generic/718 generic/719 generic/723 generic/724 generic/725 generic/728 generic/732 generic/736 generic/738 generic/741 generic/742 generic/749 generic/754 generic/758 generic/759 generic/763 generic/764 generic/771
Failed 156 of 767 tests

I needed to exclude generic/740 and generic/753. I am not completely sure what is wrong with generic/740 (it could be glitch on my side). But generic/753 fills the system log with bunch of errors:

2025-11-12T18:36:24.171533-08:00 hfsplus-testing-0001 root: run xfstest
generic/753
2025-11-12T18:36:24.175432-08:00 hfsplus-testing-0001 kernel: run fstests
generic/753 at 2025-11-12 18:36:24
2025-11-12T18:36:24.243745-08:00 hfsplus-testing-0001 systemd[1]: Started
fstests-generic-753.scope - /usr/bin/bash -c "test -w
 /proc/self/oom_score_adj && echo 250 > /proc/self/oom_score_adj; exec
./tests/generic/753".
2025-11-12T18:36:26.068288-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0):
segctord starting. Construction interval = 5 second
s, CP frequency < 30 seconds
2025-11-12T18:36:26.082067-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
start
2025-11-12T18:36:26.082949-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
pause (clean check)
2025-11-12T18:36:28.111323-08:00 hfsplus-testing-0001 kernel: Buffer I/O error

on dev dm-0, logical block 2621424, async page r
ead

...

Quoted 4 lines
2025-11-12T18:36:28.398430-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O

error writing log (start-blocknr=49152, block-c
ount=418) in segment 24

Quoted 8 lines
Quoted 3 lines

I need to double check but likewise error happens not only for generic/753 test- case. As far as I can see, other test-cases also triggered such issue. But namely generic/753 hangs infinitely with such error messages.

Okay, I'll take a look at xfstests/753 and related tests. To be honest, I've been busy lately and haven't had much time, but I hope to have some time after Tuesday.

It's OK. We are not in a hurry. And it's a lot of tests are failing right now.

Quoted 24 lines
Quoted 5 lines

I believe it makes sense to account all of these issues in some tracking system before starting to fix it. Are you using any tracking system for NILFS2 issues? Frankly speaking, I am using github's tracking system for HFS/HFS+ issues [1]. It's simple enough but I don't need in more complex system for this right now. So, what do you think about some bug tracking system for NILFS2?

We don't have a central BTS that we operate. We did have one during development, but it wasn't open and is no longer usable. So we either use a mailing list or syzbot, and although I don't particularly want or use it, nilfs-utils' github plays a role in that regard.

As for managing issues raised by xfstests, as you say, I agree that a proper BTS is needed.
However, something that is heavily web-dependent like github doesn't work well with mailing lists, so I'm honestly not sure if it's a good solution for this project, apart from github-based development projects.

In this regard, I think syzbot is good, because email exchanges naturally become a response history and are easily shared with the mailing list.
Unfortunately, it doesn't cover the entire issue tracking.

Quoted 6 lines
Quoted 4 lines

If you're going to use github for issue tracking, it would be better if it could be set up to be highly compatible with mailing lists. What do you think?

I like your suggestion. But what particular BTS candidate do you have in mind?

Github comes to mind here.
When you use GitHub for HFS/HFS+, do you apply any special approach to tie it into the mailing-list workflow?
Or do you treat it as a completely separate tool?

Quoted 8 lines
Quoted 5 lines

Personally, I'd like to see a better issue tracking system that can bridge with email-driven workflows, flexibly connect with AI, and support OSS activity, but I don't know of anything other than GitHub that I think would be suitable.

So, this is my worry that we could not find good and free BTS. And, finally, we will need to use anything not very good but accessible right now. :)

Yes, that’s probably how it will end up.

Quoted 10 lines
Quoted 9 lines
Quoted 2 lines

As far as I can see, syzbot still reports about 5 issues for NILFS2 [2]. So, it makes sense to account these issues too.

I think it's fine to use it solely for issue management purposes, as long as it doesn't result in double management. Therefore, I think we should make sure to always jump to syzbot from GitHub, etc., as an index, and make good use of syzbot's workflow as is.

Quoted 3 lines

I am simply thinking to have some tracking system that can account all NILFS2 issues. The syzbot has its own tracking system. But, from my point of view, it makes sense to account syzbot issues like sub-class of issues.

I don’t think there’s any difference in our thinking.

You mean using GitHub or some other tool to manage the overall set of issues, right?
Issues from syzbot would be handled primarily within syzbot, but we would use GitHub or similar as an index alongside other issues. That approach sounds good to me.

I'm still looking for good BTS, but it might be quicker to start making them on github now.

Thanks,
Ryusuke Konishi

#4 lore raw
Quoted 119 lines · Ryusuke Konishi
Quoted 118 lines · Viacheslav Dubeyko

Hi Ryusuke,

Quoted 74 lines · Ryusuke Konishi

Hi Viacheslav,

Quoted 66 lines · Viacheslav Dubeyko

Hi Ryusuke,

I did run the xfstests suite for NILFS2. As far as I can see, there are 156 failed tests and I needed to exclude 2 tests from running.

sudo ./check -g auto -E ./my_exclude.txt
FSTYP -- nilfs2
PLATFORM -- Linux/x86_64 hfsplus-testing-0001 6.18.0-rc3+ #93 SMP
PREEMPT_DYNAMIC Wed Nov 12 14:37:49 PST 2025
MKFS_OPTIONS -- /dev/loop51
MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch

<skipped>

Failures: generic/003 generic/040 generic/041 generic/068 generic/074 generic/075 generic/078 generic/080 generic/086 generic/092 generic/097 generic/099 generic/100 generic/103 generic/105 generic/109 generic/112 generic/117 generic/121 generic/122 generic/124 generic/127 generic/129 generic/131 generic/136 generic/177 generic/182 generic/192 generic/215 generic/221 generic/237 generic/241 generic/245 generic/246 generic/247 generic/248 generic/249 generic/251 generic/255 generic/257 generic/258 generic/260 generic/285 generic/286 generic/307 generic/309 generic/310 generic/313 generic/316 generic/318 generic/319 generic/322 generic/337 generic/348 generic/360 generic/363 generic/365 generic/375 generic/376 generic/377 generic/394 generic/403 generic/404 generic/408 generic/409 generic/410 generic/411 generic/420 generic/425 generic/428 generic/430 generic/431 generic/432 generic/433 generic/436 generic/437 generic/438 generic/439 generic/443 generic/444 generic/445 generic/448 generic/469 generic/471 generic/478 generic/483 generic/484 generic/485 generic/486 generic/489 generic/490 generic/503 generic/504 generic/510 generic/512 generic/516 generic/519 generic/523 generic/529 generic/533 generic/535 generic/537 generic/539 generic/547 generic/553 generic/555 generic/563 generic/565 generic/567 generic/568 generic/571 generic/585 generic/589 generic/590 generic/607 generic/610 generic/611 generic/614 generic/616 generic/618 generic/629 generic/631 generic/632 generic/634 generic/637 generic/638 generic/639 generic/640 generic/650 generic/676 generic/690 generic/695 generic/697 generic/704 generic/706 generic/712 generic/713 generic/715 generic/718 generic/719 generic/723 generic/724 generic/725 generic/728 generic/732 generic/736 generic/738 generic/741 generic/742 generic/749 generic/754 generic/758 generic/759 generic/763 generic/764 generic/771
Failed 156 of 767 tests

I needed to exclude generic/740 and generic/753. I am not completely sure what is wrong with generic/740 (it could be glitch on my side). But generic/753 fills the system log with bunch of errors:

2025-11-12T18:36:24.171533-08:00 hfsplus-testing-0001 root: run xfstest
generic/753
2025-11-12T18:36:24.175432-08:00 hfsplus-testing-0001 kernel: run fstests
generic/753 at 2025-11-12 18:36:24
2025-11-12T18:36:24.243745-08:00 hfsplus-testing-0001 systemd[1]: Started
fstests-generic-753.scope - /usr/bin/bash -c "test -w
 /proc/self/oom_score_adj && echo 250 > /proc/self/oom_score_adj; exec
./tests/generic/753".
2025-11-12T18:36:26.068288-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0):
segctord starting. Construction interval = 5 second
s, CP frequency < 30 seconds
2025-11-12T18:36:26.082067-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
start
2025-11-12T18:36:26.082949-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
pause (clean check)
2025-11-12T18:36:28.111323-08:00 hfsplus-testing-0001 kernel: Buffer I/O error

on dev dm-0, logical block 2621424, async page r
ead

...

Quoted 4 lines
2025-11-12T18:36:28.398430-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O

error writing log (start-blocknr=49152, block-c
ount=418) in segment 24

Quoted 8 lines
Quoted 3 lines

I need to double check but likewise error happens not only for generic/753 test- case. As far as I can see, other test-cases also triggered such issue. But namely generic/753 hangs infinitely with such error messages.

Okay, I'll take a look at xfstests/753 and related tests. To be honest, I've been busy lately and haven't had much time, but I hope to have some time after Tuesday.

It's OK. We are not in a hurry. And it's a lot of tests are failing right now.

Quoted 28 lines
Quoted 5 lines

I believe it makes sense to account all of these issues in some tracking system before starting to fix it. Are you using any tracking system for NILFS2 issues? Frankly speaking, I am using github's tracking system for HFS/HFS+ issues [1]. It's simple enough but I don't need in more complex system for this right now. So, what do you think about some bug tracking system for NILFS2?

We don't have a central BTS that we operate. We did have one during development, but it wasn't open and is no longer usable. So we either use a mailing list or syzbot, and although I don't particularly want or use it, nilfs-utils' github plays a role in that regard.

As for managing issues raised by xfstests, as you say, I agree that a proper BTS is needed.
However, something that is heavily web-dependent like github doesn't work well with mailing lists, so I'm honestly not sure if it's a good solution for this project, apart from github-based development projects.

In this regard, I think syzbot is good, because email exchanges naturally become a response history and are easily shared with the mailing list.
Unfortunately, it doesn't cover the entire issue tracking.

If you're going to use github for issue tracking, it would be better if it could be set up to be highly compatible with mailing lists. What do you think?

Quoted 7 lines
Quoted 1 line

I like your suggestion. But what particular BTS candidate do you have in mind?

Github comes to mind here.
When you use GitHub for HFS/HFS+, do you apply any special approach to tie it into the mailing-list workflow?
Or do you treat it as a completely separate tool?

Frankly speaking, I simply needed something as fast as possible at that time. :) I created github repository for managing HFS/HFS+ patches before I had repository on kernel.org. And I realized that github has pretty simple tracking system that integrated into repository. I didn't think about integration of it into mailing-list workflow. Anybody can add link on issue into patch and leave any number of comments in the issue's ticket. I considered that it's good enough. I assume that in your terminology I am using it as separate tool.

Also, github's tracking system provides the opportunity to assign the issue on people. And it is possible classify issues on project/feature basis. So, it's simple but reasonable not bad, from my point of view.

But how do you imagine integration into mailing-list workflow? Could bugzilla provide the necessary features?

Quoted 11 lines
Quoted 8 lines
Quoted 5 lines

Personally, I'd like to see a better issue tracking system that can bridge with email-driven workflows, flexibly connect with AI, and support OSS activity, but I don't know of anything other than GitHub that I think would be suitable.

So, this is my worry that we could not find good and free BTS. And, finally, we will need to use anything not very good but accessible right now. :)

Yes, that’s probably how it will end up.

AI becomes more powerful with every day. So, I don's see any problem for AI to digest even github's issue system. :)

Quoted 16 lines
Quoted 10 lines
Quoted 9 lines
Quoted 2 lines

As far as I can see, syzbot still reports about 5 issues for NILFS2 [2]. So, it makes sense to account these issues too.

I think it's fine to use it solely for issue management purposes, as long as it doesn't result in double management. Therefore, I think we should make sure to always jump to syzbot from GitHub, etc., as an index, and make good use of syzbot's workflow as is.

Quoted 3 lines

I am simply thinking to have some tracking system that can account all NILFS2 issues. The syzbot has its own tracking system. But, from my point of view, it makes sense to account syzbot issues like sub-class of issues.

I don’t think there’s any difference in our thinking.

Quoted 10 lines

You mean using GitHub or some other tool to manage the overall set of issues, right?
Issues from syzbot would be handled primarily within syzbot, but we would use GitHub or similar as an index alongside other issues. That approach sounds good to me.

I'm still looking for good BTS, but it might be quicker to start making them on github now.

This was my point. :)

Probably, you need to enable the issue system for NILFS2 on github somehow. Because, currently, I don't see anything available. And I don't remember already how I did it.

Thanks,
Slava.

maintainer
#5 lore raw
Quoted 137 lines · Viacheslav Dubeyko
Quoted 119 lines · Ryusuke Konishi
Quoted 118 lines · Viacheslav Dubeyko

Hi Ryusuke,

Quoted 74 lines · Ryusuke Konishi

Hi Viacheslav,

Quoted 66 lines · Viacheslav Dubeyko

Hi Ryusuke,

I did run the xfstests suite for NILFS2. As far as I can see, there are 156 failed tests and I needed to exclude 2 tests from running.

sudo ./check -g auto -E ./my_exclude.txt
FSTYP -- nilfs2
PLATFORM -- Linux/x86_64 hfsplus-testing-0001 6.18.0-rc3+ #93 SMP
PREEMPT_DYNAMIC Wed Nov 12 14:37:49 PST 2025
MKFS_OPTIONS -- /dev/loop51
MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch

<skipped>

Failures: generic/003 generic/040 generic/041 generic/068 generic/074 generic/075 generic/078 generic/080 generic/086 generic/092 generic/097 generic/099 generic/100 generic/103 generic/105 generic/109 generic/112 generic/117 generic/121 generic/122 generic/124 generic/127 generic/129 generic/131 generic/136 generic/177 generic/182 generic/192 generic/215 generic/221 generic/237 generic/241 generic/245 generic/246 generic/247 generic/248 generic/249 generic/251 generic/255 generic/257 generic/258 generic/260 generic/285 generic/286 generic/307 generic/309 generic/310 generic/313 generic/316 generic/318 generic/319 generic/322 generic/337 generic/348 generic/360 generic/363 generic/365 generic/375 generic/376 generic/377 generic/394 generic/403 generic/404 generic/408 generic/409 generic/410 generic/411 generic/420 generic/425 generic/428 generic/430 generic/431 generic/432 generic/433 generic/436 generic/437 generic/438 generic/439 generic/443 generic/444 generic/445 generic/448 generic/469 generic/471 generic/478 generic/483 generic/484 generic/485 generic/486 generic/489 generic/490 generic/503 generic/504 generic/510 generic/512 generic/516 generic/519 generic/523 generic/529 generic/533 generic/535 generic/537 generic/539 generic/547 generic/553 generic/555 generic/563 generic/565 generic/567 generic/568 generic/571 generic/585 generic/589 generic/590 generic/607 generic/610 generic/611 generic/614 generic/616 generic/618 generic/629 generic/631 generic/632 generic/634 generic/637 generic/638 generic/639 generic/640 generic/650 generic/676 generic/690 generic/695 generic/697 generic/704 generic/706 generic/712 generic/713 generic/715 generic/718 generic/719 generic/723 generic/724 generic/725 generic/728 generic/732 generic/736 generic/738 generic/741 generic/742 generic/749 generic/754 generic/758 generic/759 generic/763 generic/764 generic/771
Failed 156 of 767 tests

I needed to exclude generic/740 and generic/753. I am not completely sure what is wrong with generic/740 (it could be glitch on my side). But generic/753 fills the system log with bunch of errors:

2025-11-12T18:36:24.171533-08:00 hfsplus-testing-0001 root: run xfstest
generic/753
2025-11-12T18:36:24.175432-08:00 hfsplus-testing-0001 kernel: run fstests
generic/753 at 2025-11-12 18:36:24
2025-11-12T18:36:24.243745-08:00 hfsplus-testing-0001 systemd[1]: Started
fstests-generic-753.scope - /usr/bin/bash -c "test -w
 /proc/self/oom_score_adj && echo 250 > /proc/self/oom_score_adj; exec
./tests/generic/753".
2025-11-12T18:36:26.068288-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0):
segctord starting. Construction interval = 5 second
s, CP frequency < 30 seconds
2025-11-12T18:36:26.082067-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
start
2025-11-12T18:36:26.082949-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
pause (clean check)
2025-11-12T18:36:28.111323-08:00 hfsplus-testing-0001 kernel: Buffer I/O error

on dev dm-0, logical block 2621424, async page r
ead

...

Quoted 4 lines
2025-11-12T18:36:28.398430-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O

error writing log (start-blocknr=49152, block-c
ount=418) in segment 24

Quoted 8 lines
Quoted 3 lines

I need to double check but likewise error happens not only for generic/753 test- case. As far as I can see, other test-cases also triggered such issue. But namely generic/753 hangs infinitely with such error messages.

Okay, I'll take a look at xfstests/753 and related tests. To be honest, I've been busy lately and haven't had much time, but I hope to have some time after Tuesday.

It's OK. We are not in a hurry. And it's a lot of tests are failing right now.

Quoted 28 lines
Quoted 5 lines

I believe it makes sense to account all of these issues in some tracking system before starting to fix it. Are you using any tracking system for NILFS2 issues? Frankly speaking, I am using github's tracking system for HFS/HFS+ issues [1]. It's simple enough but I don't need in more complex system for this right now. So, what do you think about some bug tracking system for NILFS2?

We don't have a central BTS that we operate. We did have one during development, but it wasn't open and is no longer usable. So we either use a mailing list or syzbot, and although I don't particularly want or use it, nilfs-utils' github plays a role in that regard.

As for managing issues raised by xfstests, as you say, I agree that a proper BTS is needed.
However, something that is heavily web-dependent like github doesn't work well with mailing lists, so I'm honestly not sure if it's a good solution for this project, apart from github-based development projects.

In this regard, I think syzbot is good, because email exchanges naturally become a response history and are easily shared with the mailing list.
Unfortunately, it doesn't cover the entire issue tracking.

If you're going to use github for issue tracking, it would be better if it could be set up to be highly compatible with mailing lists. What do you think?

Quoted 7 lines
Quoted 1 line

I like your suggestion. But what particular BTS candidate do you have in mind?

Github comes to mind here.
When you use GitHub for HFS/HFS+, do you apply any special approach to tie it into the mailing-list workflow?
Or do you treat it as a completely separate tool?

Frankly speaking, I simply needed something as fast as possible at that time. :) I created github repository for managing HFS/HFS+ patches before I had repository on kernel.org. And I realized that github has pretty simple tracking system that integrated into repository. I didn't think about integration of it into mailing-list workflow. Anybody can add link on issue into patch and leave any number of comments in the issue's ticket. I considered that it's good enough. I assume that in your terminology I am using it as separate tool.

Quoted 6 lines

Also, github's tracking system provides the opportunity to assign the issue on people. And it is possible classify issues on project/feature basis. So, it's simple but reasonable not bad, from my point of view.

But how do you imagine integration into mailing-list workflow? Could bugzilla provide the necessary features?

Bugzilla is a system that easily integrates with mailing list workflows, which is probably why it has been in use at kernel.org for so long. However, to be honest, I don't think it's suitable for a project starting BTS now.

The requirements I envision are similar to those of syzbot. It's not difficult. Specifically,

- Interactions with the mailing list should be linked to issues, allowing for bidirectional referencing.
- Optionally, the ability to indirectly control issue tracking by sending a specific CC: email to a specific BTS-linked email address using a specific format (such as syzbot's #syz dup: or #syz fix:
control method).
- More optionally, the ability to use OSS activity support features (such as syzbot's #syz test: command, which allows us to delegate reproduction testing).
In today's world, it would be something like the ability to kick off an AI engine and request a first-stage analysis of the issue using concise natural language.

I think it would probably be a good idea to register issues on GitHub anyway, use a self-hosted n8n as the glue for example, and link GitHub and gmail (for ML integration) with an AI engine like Gemini and ChatGPT.
However, posting AI output to a public mailing list raises social responsibility issues, which is an obstacle to a public email-based workflow.
(We'll probably need a moderation mechanism in place to ensure only developer-approved content is sent to ML.)

Quoted 42 lines
Quoted 11 lines
Quoted 8 lines
Quoted 5 lines

Personally, I'd like to see a better issue tracking system that can bridge with email-driven workflows, flexibly connect with AI, and support OSS activity, but I don't know of anything other than GitHub that I think would be suitable.

So, this is my worry that we could not find good and free BTS. And, finally, we will need to use anything not very good but accessible right now. :)

Yes, that’s probably how it will end up.

AI becomes more powerful with every day. So, I don's see any problem for AI to digest even github's issue system. :)

Quoted 16 lines
Quoted 10 lines
Quoted 9 lines
Quoted 2 lines

As far as I can see, syzbot still reports about 5 issues for NILFS2 [2]. So, it makes sense to account these issues too.

I think it's fine to use it solely for issue management purposes, as long as it doesn't result in double management. Therefore, I think we should make sure to always jump to syzbot from GitHub, etc., as an index, and make good use of syzbot's workflow as is.

Quoted 3 lines

I am simply thinking to have some tracking system that can account all NILFS2 issues. The syzbot has its own tracking system. But, from my point of view, it makes sense to account syzbot issues like sub-class of issues.

I don’t think there’s any difference in our thinking.

Quoted 10 lines

You mean using GitHub or some other tool to manage the overall set of issues, right?
Issues from syzbot would be handled primarily within syzbot, but we would use GitHub or similar as an index alongside other issues. That approach sounds good to me.

I'm still looking for good BTS, but it might be quicker to start making them on github now.

Quoted 5 lines

This was my point. :)

Probably, you need to enable the issue system for NILFS2 on github somehow. Because, currently, I don't see anything available. And I don't remember already how I did it.

Okay.
I'm thinking of creating a nilfs2 (linux) clone repository at
https://github.com/nilfs-dev/ so that we can file issues there. Is that okay?

Thanks,
Ryusuke Konishi

Quoted 2 lines

Thanks,
Slava.

#6 lore raw
Quoted 220 lines · Ryusuke Konishi
Quoted 137 lines · Viacheslav Dubeyko
Quoted 119 lines · Ryusuke Konishi
Quoted 118 lines · Viacheslav Dubeyko

Hi Ryusuke,

Quoted 74 lines · Ryusuke Konishi

Hi Viacheslav,

Quoted 66 lines · Viacheslav Dubeyko

Hi Ryusuke,

I did run the xfstests suite for NILFS2. As far as I can see, there are 156 failed tests and I needed to exclude 2 tests from running.

sudo ./check -g auto -E ./my_exclude.txt
FSTYP -- nilfs2
PLATFORM -- Linux/x86_64 hfsplus-testing-0001 6.18.0-rc3+ #93 SMP
PREEMPT_DYNAMIC Wed Nov 12 14:37:49 PST 2025
MKFS_OPTIONS -- /dev/loop51
MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch

<skipped>

Failures: generic/003 generic/040 generic/041 generic/068 generic/074 generic/075 generic/078 generic/080 generic/086 generic/092 generic/097 generic/099 generic/100 generic/103 generic/105 generic/109 generic/112 generic/117 generic/121 generic/122 generic/124 generic/127 generic/129 generic/131 generic/136 generic/177 generic/182 generic/192 generic/215 generic/221 generic/237 generic/241 generic/245 generic/246 generic/247 generic/248 generic/249 generic/251 generic/255 generic/257 generic/258 generic/260 generic/285 generic/286 generic/307 generic/309 generic/310 generic/313 generic/316 generic/318 generic/319 generic/322 generic/337 generic/348 generic/360 generic/363 generic/365 generic/375 generic/376 generic/377 generic/394 generic/403 generic/404 generic/408 generic/409 generic/410 generic/411 generic/420 generic/425 generic/428 generic/430 generic/431 generic/432 generic/433 generic/436 generic/437 generic/438 generic/439 generic/443 generic/444 generic/445 generic/448 generic/469 generic/471 generic/478 generic/483 generic/484 generic/485 generic/486 generic/489 generic/490 generic/503 generic/504 generic/510 generic/512 generic/516 generic/519 generic/523 generic/529 generic/533 generic/535 generic/537 generic/539 generic/547 generic/553 generic/555 generic/563 generic/565 generic/567 generic/568 generic/571 generic/585 generic/589 generic/590 generic/607 generic/610 generic/611 generic/614 generic/616 generic/618 generic/629 generic/631 generic/632 generic/634 generic/637 generic/638 generic/639 generic/640 generic/650 generic/676 generic/690 generic/695 generic/697 generic/704 generic/706 generic/712 generic/713 generic/715 generic/718 generic/719 generic/723 generic/724 generic/725 generic/728 generic/732 generic/736 generic/738 generic/741 generic/742 generic/749 generic/754 generic/758 generic/759 generic/763 generic/764 generic/771
Failed 156 of 767 tests

I needed to exclude generic/740 and generic/753. I am not completely sure what is wrong with generic/740 (it could be glitch on my side). But generic/753 fills the system log with bunch of errors:

2025-11-12T18:36:24.171533-08:00 hfsplus-testing-0001 root: run xfstest
generic/753
2025-11-12T18:36:24.175432-08:00 hfsplus-testing-0001 kernel: run fstests
generic/753 at 2025-11-12 18:36:24
2025-11-12T18:36:24.243745-08:00 hfsplus-testing-0001 systemd[1]: Started
fstests-generic-753.scope - /usr/bin/bash -c "test -w
 /proc/self/oom_score_adj && echo 250 > /proc/self/oom_score_adj; exec
./tests/generic/753".
2025-11-12T18:36:26.068288-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0):
segctord starting. Construction interval = 5 second
s, CP frequency < 30 seconds
2025-11-12T18:36:26.082067-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
start
2025-11-12T18:36:26.082949-08:00 hfsplus-testing-0001 nilfs_cleanerd[763354]:
pause (clean check)
2025-11-12T18:36:28.111323-08:00 hfsplus-testing-0001 kernel: Buffer I/O error

on dev dm-0, logical block 2621424, async page r
ead

...

Quoted 4 lines
2025-11-12T18:36:28.398430-08:00 hfsplus-testing-0001 kernel: NILFS (dm-0): I/O

error writing log (start-blocknr=49152, block-c
ount=418) in segment 24

Quoted 8 lines
Quoted 3 lines

I need to double check but likewise error happens not only for generic/753 test- case. As far as I can see, other test-cases also triggered such issue. But namely generic/753 hangs infinitely with such error messages.

Okay, I'll take a look at xfstests/753 and related tests. To be honest, I've been busy lately and haven't had much time, but I hope to have some time after Tuesday.

It's OK. We are not in a hurry. And it's a lot of tests are failing right now.

Quoted 28 lines
Quoted 5 lines

I believe it makes sense to account all of these issues in some tracking system before starting to fix it. Are you using any tracking system for NILFS2 issues? Frankly speaking, I am using github's tracking system for HFS/HFS+ issues [1]. It's simple enough but I don't need in more complex system for this right now. So, what do you think about some bug tracking system for NILFS2?

We don't have a central BTS that we operate. We did have one during development, but it wasn't open and is no longer usable. So we either use a mailing list or syzbot, and although I don't particularly want or use it, nilfs-utils' github plays a role in that regard.

As for managing issues raised by xfstests, as you say, I agree that a proper BTS is needed.
However, something that is heavily web-dependent like github doesn't work well with mailing lists, so I'm honestly not sure if it's a good solution for this project, apart from github-based development projects.

In this regard, I think syzbot is good, because email exchanges naturally become a response history and are easily shared with the mailing list.
Unfortunately, it doesn't cover the entire issue tracking.

If you're going to use github for issue tracking, it would be better if it could be set up to be highly compatible with mailing lists. What do you think?

Quoted 7 lines
Quoted 1 line

I like your suggestion. But what particular BTS candidate do you have in mind?

Github comes to mind here.
When you use GitHub for HFS/HFS+, do you apply any special approach to tie it into the mailing-list workflow?
Or do you treat it as a completely separate tool?

Frankly speaking, I simply needed something as fast as possible at that time. :) I created github repository for managing HFS/HFS+ patches before I had repository on kernel.org. And I realized that github has pretty simple tracking system that integrated into repository. I didn't think about integration of it into mailing-list workflow. Anybody can add link on issue into patch and leave any number of comments in the issue's ticket. I considered that it's good enough. I assume that in your terminology I am using it as separate tool.

Quoted 6 lines

Also, github's tracking system provides the opportunity to assign the issue on people. And it is possible classify issues on project/feature basis. So, it's simple but reasonable not bad, from my point of view.

But how do you imagine integration into mailing-list workflow? Could bugzilla provide the necessary features?

Bugzilla is a system that easily integrates with mailing list workflows, which is probably why it has been in use at kernel.org for so long. However, to be honest, I don't think it's suitable for a project starting BTS now.

The requirements I envision are similar to those of syzbot. It's not difficult. Specifically,

- Interactions with the mailing list should be linked to issues, allowing for bidirectional referencing.
- Optionally, the ability to indirectly control issue tracking by sending a specific CC: email to a specific BTS-linked email address using a specific format (such as syzbot's #syz dup: or #syz fix:
control method).
- More optionally, the ability to use OSS activity support features (such as syzbot's #syz test: command, which allows us to delegate reproduction testing).
In today's world, it would be something like the ability to kick off an AI engine and request a first-stage analysis of the issue using concise natural language.

I think it would probably be a good idea to register issues on GitHub anyway, use a self-hosted n8n as the glue for example, and link GitHub and gmail (for ML integration) with an AI engine like Gemini and ChatGPT.
However, posting AI output to a public mailing list raises social responsibility issues, which is an obstacle to a public email-based workflow.
(We'll probably need a moderation mechanism in place to ensure only developer-approved content is sent to ML.)

Quoted 44 lines
Quoted 11 lines
Quoted 8 lines
Quoted 5 lines

Personally, I'd like to see a better issue tracking system that can bridge with email-driven workflows, flexibly connect with AI, and support OSS activity, but I don't know of anything other than GitHub that I think would be suitable.

So, this is my worry that we could not find good and free BTS. And, finally, we will need to use anything not very good but accessible right now. :)

Yes, that’s probably how it will end up.

AI becomes more powerful with every day. So, I don's see any problem for AI to digest even github's issue system. :)

Quoted 16 lines
Quoted 10 lines
Quoted 9 lines
Quoted 2 lines

As far as I can see, syzbot still reports about 5 issues for NILFS2 [2]. So, it makes sense to account these issues too.

I think it's fine to use it solely for issue management purposes, as long as it doesn't result in double management. Therefore, I think we should make sure to always jump to syzbot from GitHub, etc., as an index, and make good use of syzbot's workflow as is.

Quoted 3 lines

I am simply thinking to have some tracking system that can account all NILFS2 issues. The syzbot has its own tracking system. But, from my point of view, it makes sense to account syzbot issues like sub-class of issues.

I don’t think there’s any difference in our thinking.

Quoted 10 lines

You mean using GitHub or some other tool to manage the overall set of issues, right?
Issues from syzbot would be handled primarily within syzbot, but we would use GitHub or similar as an index alongside other issues. That approach sounds good to me.

I'm still looking for good BTS, but it might be quicker to start making them on github now.

This was my point. :)

Quoted 10 lines
Quoted 3 lines

Probably, you need to enable the issue system for NILFS2 on github somehow. Because, currently, I don't see anything available. And I don't remember already how I did it.

Okay.
I'm thinking of creating a nilfs2 (linux) clone repository at
https://github.com/nilfs-dev/ so that we can file issues there.
Is that okay?

Yes, makes sense. Looks like a good place for collaboration.

Thanks,
Slava.

maintainer
#7 lore raw
Quoted 23 lines · Viacheslav Dubeyko
Quoted 10 lines · Ryusuke Konishi
Quoted 9 lines · Viacheslav Dubeyko
Quoted 4 lines · Ryusuke Konishi

I'm still looking for good BTS, but it might be quicker to start making them on github now.

This was my point. :)

Quoted 10 lines
Quoted 3 lines

Probably, you need to enable the issue system for NILFS2 on github somehow. Because, currently, I don't see anything available. And I don't remember already how I did it.

Okay.
I'm thinking of creating a nilfs2 (linux) clone repository at
https://github.com/nilfs-dev/ so that we can file issues there.
Is that okay?

Quoted 4 lines

Yes, makes sense. Looks like a good place for collaboration.

Thanks,
Slava.

I've set up an issue tracker on GitHub. It's at the following address:

https://github.com/nilfs-dev/nilfs2/issues

For now, I have registered the syzbot issue and an issue that has been reported recently on the ML.
At the top of each issue, I've included a Link: URL with a reference to the related syzbot dashboard or email post.

What about the xfstests issues ?
Shall I add all 156 reported failures? (In that case, I'll just create separate issues and include a link to your original report for each.)

Regards,
Ryusuke Konishi

#8 lore raw
Quoted 33 lines · Ryusuke Konishi
Quoted 23 lines · Viacheslav Dubeyko
Quoted 10 lines · Ryusuke Konishi
Quoted 9 lines · Viacheslav Dubeyko
Quoted 4 lines · Ryusuke Konishi

I'm still looking for good BTS, but it might be quicker to start making them on github now.

This was my point. :)

Quoted 10 lines
Quoted 3 lines

Probably, you need to enable the issue system for NILFS2 on github somehow. Because, currently, I don't see anything available. And I don't remember already how I did it.

Okay.
I'm thinking of creating a nilfs2 (linux) clone repository at
https://github.com/nilfs-dev/ so that we can file issues there.
Is that okay?

Quoted 4 lines

Yes, makes sense. Looks like a good place for collaboration.

Thanks,
Slava.

I've set up an issue tracker on GitHub. It's at the following address:

https://github.com/nilfs-dev/nilfs2/issues

Quoted 9 lines

For now, I have registered the syzbot issue and an issue that has been reported recently on the ML.
At the top of each issue, I've included a Link: URL with a reference to the related syzbot dashboard or email post.

What about the xfstests issues ?
Shall I add all 156 reported failures? (In that case, I'll just create separate issues and include a link to your original report for each.)

Great! Let me check that I can access it.

I believe that it makes sense to create a dedicated ticket with enough details for every failed test. I am ready to create these tickets but it is not quick process. So, we can do it in parallel. I could be not very productive during these and the next week because I am going to spend time for preparation and attending LPC 2025.

Thanks,
Slava.

maintainer
#9 lore raw
Quoted 47 lines · Viacheslav Dubeyko
Quoted 33 lines · Ryusuke Konishi
Quoted 23 lines · Viacheslav Dubeyko
Quoted 10 lines · Ryusuke Konishi
Quoted 9 lines · Viacheslav Dubeyko
Quoted 4 lines · Ryusuke Konishi

I'm still looking for good BTS, but it might be quicker to start making them on github now.

This was my point. :)

Quoted 10 lines
Quoted 3 lines

Probably, you need to enable the issue system for NILFS2 on github somehow. Because, currently, I don't see anything available. And I don't remember already how I did it.

Okay.
I'm thinking of creating a nilfs2 (linux) clone repository at
https://github.com/nilfs-dev/ so that we can file issues there.
Is that okay?

Quoted 4 lines

Yes, makes sense. Looks like a good place for collaboration.

Thanks,
Slava.

I've set up an issue tracker on GitHub. It's at the following address:

https://github.com/nilfs-dev/nilfs2/issues

Quoted 9 lines

For now, I have registered the syzbot issue and an issue that has been reported recently on the ML.
At the top of each issue, I've included a Link: URL with a reference to the related syzbot dashboard or email post.

What about the xfstests issues ?
Shall I add all 156 reported failures? (In that case, I'll just create separate issues and include a link to your original report for each.)

Great! Let me check that I can access it.

Quoted 8 lines

I believe that it makes sense to create a dedicated ticket with enough details for every failed test. I am ready to create these tickets but it is not quick process. So, we can do it in parallel. I could be not very productive during these and the next week because I am going to spend time for preparation and attending LPC 2025.

Thanks,
Slava.

Well, as for the schedule, the merge window has begun and LPC 2025 is coming up, so you'll probably be busy, so please proceed independently at your own convenience.

For now, I've labeled the registered issues with xfstests.

It seems to be working without any restrictions for now, but please let me know if you have any problems operating the issues.

Thanks,
Ryusuke Konishi

#10 lore raw

Hi Ryusuke,

Quoted 75 lines · Ryusuke Konishi
Quoted 66 lines · Viacheslav Dubeyko
Quoted 45 lines · Ryusuke Konishi
Quoted 27 lines · Viacheslav Dubeyko
Quoted 17 lines · Ryusuke Konishi
Quoted 8 lines · Viacheslav Dubeyko
Quoted 5 lines · Ryusuke Konishi

I'm still looking for good BTS, but it might be quicker to start
making them on github now.

Quoted 7 lines

This was my point. :)

Probably, you need to enable the issue system for NILFS2 on github somehow.
Because, currently, I don't see anything available. And I don't remember already
how I did it.

Quoted 7 lines

Okay.
I'm thinking of creating a nilfs2 (linux) clone repository at
https://github.com/nilfs-dev/     so that we can file issues there.
Is that okay?

Quoted 4 lines

Yes, makes sense. Looks like a good place for collaboration.

Thanks,
Slava.

I've set up an issue tracker on GitHub. It's at the following address:

https://github.com/nilfs-dev/nilfs2/issues

For now, I have registered the syzbot issue and an issue that has been
reported recently on the ML.
At the top of each issue, I've included a Link: URL with a reference
to the related syzbot dashboard or email post.

Quoted 6 lines

What about the xfstests issues ?
Shall I add all 156 reported failures? (In that case, I'll just create
separate issues and include a link to your original report for each.)

Great! Let me check that I can access it.

I believe that it makes sense to create a dedicated ticket with enough details
for every failed test. I am ready to create these tickets but it is not quick
process. So, we can do it in parallel. I could be not very productive during
these and the next week because I am going to spend time for preparation and
attending LPC 2025.

Quoted 2 lines

Thanks,
Slava.

Well, as for the schedule, the merge window has begun and LPC 2025 is coming up, so you'll probably be busy, so please proceed independently
at your own convenience.

Quoted 6 lines

For now, I've labeled the registered issues with xfstests.

It seems to be working without any restrictions for now, but please let me know if you have any problems operating the issues.

I've created the tickets for all xfestests' issues that I was able to detect. As far as I can see, I can stably reproduce around 50 issues. I suppose that the rest ones are side effects of other failures or, maybe, it cannot be reproduced in stable manner. Anyway, it makes sense to account these issues too for checking what is wrong there. If there is nothing interesting there, we can simply close these issues.

So, I can start to analyze the issues now. :)

Thanks,
Slava.