Open win32asm opened 4 months ago
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
/feature
CONFIG_SQUASHFS_XZ
is already enabled in the WSL2 kernel, along with other XZ
options. See details at:
XZ-enabled squashfs can be mounted, but respective XZ BCJ filtering algorithms are disabled.
From your reference:
CONFIG_XZ_DEC=y
# CONFIG_XZ_DEC_X86 is not set
# CONFIG_XZ_DEC_POWERPC is not set
# CONFIG_XZ_DEC_IA64 is not set
# CONFIG_XZ_DEC_ARM is not set
# CONFIG_XZ_DEC_ARMTHUMB is not set
# CONFIG_XZ_DEC_SPARC is not set
# CONFIG_XZ_DEC_TEST is not set
I believe it is CONFIG_XZ_DEC_X86 that fails in my case.
For reference: the same issue was encountered before - https://github.com/microsoft/WSL/issues/9668
Recompiling the kernel with CONFIG_XZ_DEC_X86=y
solved the problem.
Is your feature request related to a problem? Please describe. Modern distributions (e.g. RH) enable CONFIG_XZ_DEC_X86=y CONFIG_XZ_DEC_POWERPC=y CONFIG_XZ_DEC_IA64=y CONFIG_XZ_DEC_ARM=y CONFIG_XZ_DEC_ARMTHUMB=y CONFIG_XZ_DEC_SPARC=y CONFIG_XZ_DEC_BCJ=y in their kernel configuration. This allows them to mount squashfs filesystems created anywhere. Default WSL kernel returns IO error with a 'helpful' message of
recompiling the WSL kernel with above settings fixes the problem.
Describe the solution you'd like Enabling the kernel compilation options is a low-cost solution not leading to code bloat and allows to process various squashfs entries with default WSL kernel.
Describe alternatives you've considered given that squashfs may come from any source, alternative is to unpack squashfs with userlevel tools before using. squashfs could have high compression ratios, resulting in unneededly high disk usage.
Additional context none
Thanks.