Should we consider disable generic/563 for file systems that do not support cgroup2?

Viacheslav Dubeyko <[email protected]> Fri, 10 Jul 2026 19:10:43 +0000
Newsgroups org.kernel.vger.fstests,org.kernel.vger.linux-fsdevel
Message-ID <[email protected]>
Hello,

As far as I can see, the generic/563 test is dedicated to cgroup v2
functionality. And several file systems fails to execute the test:

sudo ./check generic/563
FSTYP         -- hfsplus
PLATFORM      -- Linux/x86_64 hfsplus-testing-0001 7.2.0-rc1+ #55 SMP
PREEMPT_DYNAMIC Fri Jul 10 11:21:38 PDT 2026
MKFS_OPTIONS  -- /dev/loop51
MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch

generic/563        - output mismatch (see xfstests-
dev/results//generic/563.out.bad)
    --- tests/generic/563.out	2026-04-07 14:19:04.785079940 -0700
    +++ xfstests-dev/results//generic/563.out.bad	2026-07-10
11:33:14.231562955 -0700
    @@ -4,11 +4,13 @@
     write is in range
     write -> read/write
     read is in range
    -write is in range
    +write has value of 0
    +write is NOT in range 15938355.2 .. 17616076.8
     read is in range
    ...
    (Run 'diff -u xfstests-dev/tests/generic/563.out xfstests-
dev/results//generic/563.out.bad'  to see the entire diff)
Ran: generic/563
Failures: generic/563
Failed 1 of 1 tests

sudo ./check generic/563
FSTYP         -- vfat
PLATFORM      -- Linux/x86_64 hfsplus-testing-0001 7.2.0-rc1+ #55 SMP
PREEMPT_DYNAMIC Fri Jul 10 11:21:38 PDT 2026
MKFS_OPTIONS  -- /dev/loop51
MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch

generic/563        - output mismatch (see xfstests-
dev/results//generic/563.out.bad)
    --- tests/generic/563.out	2026-04-07 14:19:04.785079940 -0700
    +++ xfstests-dev/results//generic/563.out.bad	2026-07-10
11:36:02.221320239 -0700
    @@ -1,14 +1,19 @@
     QA output created by 563
     read/write
    -read is in range
    +read has value of 22014464
    +read is NOT in range 15938355.2 .. 17616076.8
     write is in range
     write -> read/write
    ...
    (Run 'diff -u xfstests-dev/tests/generic/563.out xfstests-
dev/results//generic/563.out.bad'  to see the entire diff)
Ran: generic/563
Failures: generic/563
Failed 1 of 1 tests

sudo ./check generic/563
FSTYP         -- nilfs2
PLATFORM      -- Linux/x86_64 hfsplus-testing-0001 7.2.0-rc1+ #55 SMP
PREEMPT_DYNAMIC Fri Jul 10 11:21:38 PDT 2026
MKFS_OPTIONS  -- /dev/loop51
MOUNT_OPTIONS -- /dev/loop51 /mnt/scratch

generic/563        - output mismatch (see xfstests-
dev/results//generic/563.out.bad)
    --- tests/generic/563.out	2026-04-07 14:19:04.785079940 -0700
    +++ xfstests-dev/results//generic/563.out.bad	2026-07-10
11:37:57.633280743 -0700
    @@ -1,14 +1,18 @@
     QA output created by 563
     read/write
     read is in range
    -write is in range
    +write has value of 0
    +write is NOT in range 15938355.2 .. 17616076.8
     write -> read/write
    ...
    (Run 'diff -u xfstests-dev/tests/generic/563.out xfstests-
dev/results//generic/563.out.bad'  to see the entire diff)
Ran: generic/563
Failures: generic/563
Failed 1 of 1 tests

Should file system (like HFS/HFS+, for example) implement cgroup2 support to
pass the  generic/563 successfully? Is it generic enough test-case? Should we
consider disable generic/563 for file systems that do not support cgroup2?

Thanks,
Slava.