Re: erofs pointer corruption and kernel crash

[Gao Xiang]

On 2026/4/10 18:10, Arseniy Krasnov wrote:
> 10.04.2026 13:06, Gao Xiang пишет:
> > On 2026/4/10 18:03, Arseniy Krasnov wrote:
> > > 10.04.2026 13:01, Gao Xiang пишет:
> > > > On 2026/4/10 17:59, Arseniy Krasnov wrote:
> > > > > 10.04.2026 12:20, Gao Xiang wrote:
> > > > > > 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?
> > > > >
> > > > > We have 1.8.5 erofs-utils
> > > >
> > > > 1.8.5 shouldn't have `-E48bit` support, that is my question.
> > >
> > > You mean to try to reproduce with 1.9 utils ?
> >
> > Nope, I meant
> >
> > BR2_TARGET_ROOTFS_EROFS_COMPRESSION_ALGORITHMS="zstd,22 --max-extent-bytes 65536 -E48bit"
> >
> > is invalid in erofs-utils 1.8.5.
> >
> > If you were using erofs-utils 1.9+, that may be due to
> > the new `-E48bit`;
> >
> > but you said you are using erofs-utils 1.8.5, that makes
> > me feel confused.
>
> Ah, ok, so need to debug it at kernel side as we talked before.

Sigh, you don't answer my questions:

1. so are you using `-E48bit` and newer erofs-utils verison?

2. Is "EXPERIMENTAL 48-bit layout support in use. Use at your
   own risk!" shown when mounting?

Thanks,
Gao Xiang