答复: 答复: 答复: 答复: 答复: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not integer,incompatible for ancient android devices

From: Gaoming (ming, consumer BG)
Date: Mon Jul 02 2018 - 20:59:04 EST


And can you help me understand *why* such a choice was made?
-----if there is such a problem in your devices, how will you do? Is there any other choice?
----- of course, you cannot format the partition.

-----邮件原件-----
发件人: Theodore Y. Ts'o [mailto:tytso@xxxxxxx]
发送时间: 2018年7月2日 20:17
收件人: Gaoming (ming, consumer BG)
抄送: linux-ext4@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; Liqingchao (sorp); Shenchen (harry); miaoxie (A); yangfei (D); Renlipeng (OS driver)
主题: Re: 答复: 答复: 答复: 答复: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not integer,incompatible for ancient android devices

On Mon, Jul 02, 2018 at 09:34:28AM +0000, Gaoming (ming, consumer BG) wrote:
> I got it. You hate make_ext4fs, and me too.
> You don't like to merge this patch in upstream e2fsprogs to resolve the bug of make_ext4fs.
>
> Of course we will fix the bug on our ancient devices, we have to .
> If this problem fixed or this patch merges in latest e2fsprogs, we will backport the latest e2fsprogs.
> If not, we have no motivation to backport it.
>
> I don't know whether other android devices suffer this problem.

Can you be explicit and tell me how many Huawei devices uses a block
size of 1024? And can you help me understand *why* such a choice was made?

- Ted