summaryrefslogtreecommitdiffstats
path: root/Documentation/target
diff options
context:
space:
mode:
authorJeffle Xu <jefflexu@linux.alibaba.com>2022-05-26 09:03:44 +0800
committerGao Xiang <hsiangkao@linux.alibaba.com>2022-05-29 15:34:54 +0800
commit0130e4e8e49f9bd0342d3fc14102470ea9e7230e (patch)
tree9bd7c26e13108a7cbf5b882cf079dd6ae2dd527a /Documentation/target
parent65965d9530b0c320759cd18a9a5975fb2e098462 (diff)
downloadlinux-0130e4e8e49f9bd0342d3fc14102470ea9e7230e.tar.bz2
erofs: leave compressed inodes unsupported in fscache mode for now
erofs over fscache doesn't support the compressed layout yet. It will cause NULL crash if there are compressed inodes contained when working in fscache mode. So far in the erofs based container image distribution scenarios (RAFS v6), the compressed RAFS v6 images are downloaded and then decompressed on demand as an uncompressed erofs image. Then the erofs image is mounted in fscache mode for containers to use. IOWs, currently compressed data is decompressed on the userspace side instead and uncompressed erofs images will be finally cached. The fscache support for the compressed layout is still under development and it will be used for runtime decompression feature. Anyway, to avoid the potential crash, let's leave the compressed inodes unsupported in fscache mode until we support it later. Fixes: 1442b02b66ad ("erofs: implement fscache-based data read for non-inline layout") Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com> Reviewed-by: Gao Xiang <hsiangkao@linux.alibaba.com> Reviewed-by: Chao Yu <chao@kernel.org> Link: https://lore.kernel.org/r/20220526010344.118493-1-jefflexu@linux.alibaba.com Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
Diffstat (limited to 'Documentation/target')
0 files changed, 0 insertions, 0 deletions