mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arseniy Krasnov <avkrasnov@salutedevices.com>
To: Gao Xiang <hsiangkao@linux.alibaba.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 13:10:30 +0300	[thread overview]
Message-ID: <5301be8f-4b2e-4f1d-a90b-91da00f98994@salutedevices.com> (raw)
In-Reply-To: <cad241fc-c2c6-4872-ab56-be3b7b44fbea@linux.alibaba.com>



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.

Thanks

> Thanks,
> Gao Xiang


  reply	other threads:[~2026-04-10 10:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  8:13 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
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 [this message]
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-25 15:29                 ` Gao Xiang
2026-04-26 11:42                   ` Arseniy Krasnov
2026-04-27 14:45                     ` 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=5301be8f-4b2e-4f1d-a90b-91da00f98994@salutedevices.com \
    --to=avkrasnov@salutedevices.com \
    --cc=chao@kernel.org \
    --cc=dhavale@google.com \
    --cc=hsiangkao@linux.alibaba.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

all inboxes | Powered by JetHome®