Re: [cip-dev] linux-6.12.y-cip: maintenance scope for EROFS Zstandard support

--fWbr8rqUu15+7gSa
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi!

> I am evaluating linux-6.12.y-cip for a non-member industrial Linux
> distribution using a read-only EROFS root filesystem.
>=20
> Our required configuration includes:
>=20
>     CONFIG_EROFS_FS=3Dy
>     CONFIG_EROFS_FS_ZIP=3Dy
>     CONFIG_EROFS_FS_ZIP_ZSTD=3Dy
>=20
> I understand that:
>=20
> 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.

In case of ZSTD, I don't really foresee problems. You should be able
to simply use -cip; in unlikely case there are problems you can submit
patches.

> Could you clarify the intended SLTS maintenance scope?
>=20
> - 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?
>=20
> - 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?
>=20
> - Would an upstream contribution adding explicit EROFS-Zstd functional
>   testing to the CIP test pipeline help clarify or strengthen its
>   maintenance coverage?

If EROFS_.._ZSTD is important to you, I suggest you start testing
required functionality in -cip kernels, and we can talk if you run
into problems.

But these would be questions for TSC.

Best regards,
								Pavel

--fWbr8rqUu15+7gSa
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRPfPO7r0eAhk010v0w5/Bqldv68gUCamsi+AAKCRAw5/Bqldv6
8szdAJ9E+tx+WlO1K7+H05l8C8VTNODi5wCaA2XZ6AlKfkEmBK1GxyaVtW7zBWM=
=ao98
-----END PGP SIGNATURE-----

--fWbr8rqUu15+7gSa--