From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Arseniy Krasnov <avkrasnov@salutedevices.com>
Cc: oxffffaa@gmail.com, linux-erofs@lists.ozlabs.org,
linux-kernel@vger.kernel.org, kernel@salutedevices.com,
Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org>,
Yue Hu <zbestahu@gmail.com>,
Jeffle Xu <jefflexu@linux.alibaba.com>,
Sandeep Dhavale <dhavale@google.com>,
Hongbo Li <lihongbo22@huawei.com>,
Sheng Yong <shengyong1@xiaomi.com>
Subject: Re: erofs pointer corruption and kernel crash
Date: Fri, 10 Apr 2026 17:20:50 +0800 [thread overview]
Message-ID: <16ea58e8-43b7-439b-91db-9f87d2fb2b84@linux.alibaba.com> (raw)
In-Reply-To: <9d8a073a-982e-4c7b-9445-623941a16b05@salutedevices.com>
On 2026/4/10 16:55, Arseniy Krasnov wrote:
>
>
...
>>>
>>> BR2_TARGET_ROOTFS_EROFS=y
>>> BR2_TARGET_ROOTFS_EROFS_CUSTOM_COMPRESSION=y
>>> BR2_TARGET_ROOTFS_EROFS_COMPRESSION_ALGORITHMS="zstd,22 --max-extent-bytes 65536 -E48bit"
btw, may I ask what's the erofs-utils version?
erofs-utils 1.9?
I guess it's related to a relatively new experimental
feature (-E48bit + encoded extents + zstd) introduced in v6.15.
If you don't use this new feature, the issue may not be
reproduced anymore.
Thanks,
Gao Xiang
>>> BR2_TARGET_ROOTFS_EROFS_FRAGMENTS=y
>>> BR2_TARGET_ROOTFS_EROFS_PCLUSTERSIZE=65536
>>>
>>>
>>>
>>> May be You know how to fix it or some ideas? Because we are new at erofs and need to discover and
>>> learn its source code.
>>>
>>> Thanks
>>
next prev parent reply other threads:[~2026-04-10 9:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 8:13 erofs pointer corruption and kernel crash Arseniy Krasnov
2026-04-10 8:31 ` Gao Xiang
2026-04-10 8:42 ` Gao Xiang
2026-04-10 8:51 ` Arseniy Krasnov
2026-04-10 8:59 ` Gao Xiang
2026-04-10 8:55 ` Arseniy Krasnov
2026-04-10 9:20 ` Gao Xiang [this message]
2026-04-10 9:59 ` Arseniy Krasnov
2026-04-10 10:01 ` Gao Xiang
2026-04-10 10:03 ` Arseniy Krasnov
2026-04-10 10:06 ` Gao Xiang
2026-04-10 10:10 ` Arseniy Krasnov
2026-04-10 10:22 ` Gao Xiang
2026-04-10 10:31 ` Arseniy Krasnov
2026-04-10 11:37 ` Arseniy Krasnov
2026-04-10 12:20 ` Gao Xiang
2026-04-10 13:27 ` Arseniy Krasnov
2026-04-10 15:41 ` Gao Xiang
2026-04-11 15:10 ` Arseniy Krasnov
2026-04-13 7:08 ` Gao Xiang
2026-04-13 7:20 ` Arseniy Krasnov
2026-04-10 13:35 ` Arseniy Krasnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16ea58e8-43b7-439b-91db-9f87d2fb2b84@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=avkrasnov@salutedevices.com \
--cc=chao@kernel.org \
--cc=dhavale@google.com \
--cc=jefflexu@linux.alibaba.com \
--cc=kernel@salutedevices.com \
--cc=lihongbo22@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=shengyong1@xiaomi.com \
--cc=xiang@kernel.org \
--cc=zbestahu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox