linux-6.12.y-cip: maintenance scope for EROFS Zstandard support
[email protected] Sat, 25 Jul 2026 17:35:46 +0200
| Newsgroups | org.cip-project.lists.cip-dev |
|---|---|
| Message-ID | <[email protected]> |
Hello CIP kernel maintainers,
I am evaluating linux-6.12.y-cip for a non-member industrial Linux
distribution using a read-only EROFS root filesystem.
Our required configuration includes:
CONFIG_EROFS_FS=y
CONFIG_EROFS_FS_ZIP=y
CONFIG_EROFS_FS_ZIP_ZSTD=y
I understand that:
1. EROFS and its Zstandard decoder are present in linux-6.12.y-cip.
2. EROFS is enabled in the CIP 6.12 merged and QEMU configurations,
although not in the container defconfig.
3. Linux 6.12 describes EROFS Zstandard support as experimental.
4. Upstream commit 8f2fb72fd17e ("erofs: update compression algorithm
status") subsequently promoted Zstandard out of experimental status
after more than a year of testing.
5. The CIP maintenance policy says that features labelled experimental
may potentially be excluded after upstream LTS maintenance ends.
Could you clarify the intended SLTS maintenance scope?
- Does CIP currently intend to carry applicable bug and security fixes
for EROFS core and CONFIG_EROFS_FS_ZIP_ZSTD through the projected
linux-6.12.y-cip EOL in June 2035?
- Does EROFS being enabled in the CIP merged configurations place it
within the reference maintenance scope, or is that scope limited to
configurations submitted by CIP members?
- Would an upstream contribution adding explicit EROFS-Zstd functional
testing to the CIP test pipeline help clarify or strengthen its
maintenance coverage?
I am asking about the intended public kernel maintenance scope, rather
than requesting commercial end-user support.
Thank you,
Raymond