yangfei (D); Renlipeng (OS driver)
主题: Re: 答复: 答复: 答复: 答复: 答复: 答复: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap
num not integer,incompatible for ancient android devices
On Tue, Jul 03, 2018 at 11:15:21AM +, Gaoming (ming, consumer BG) wrote:
>
> You misunderstand my question. Why was the choic
yangfei (D); Renlipeng (OS driver)
主题: Re: 答复: 答复: 答复: 答复: 答复: 答复: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap
num not integer,incompatible for ancient android devices
On Tue, Jul 03, 2018 at 11:15:21AM +, Gaoming (ming, consumer BG) wrote:
>
> You misunderstand my question. Why was the choic
On Tue, Jul 03, 2018 at 11:15:21AM +, Gaoming (ming, consumer BG) wrote:
>
> You misunderstand my question. Why was the choice of a blocksize of
> 1024 made?
>
> -some one choose, not me . I guess they want get more inodes in 20M
> filesystem.
That can't be the explanation.
I just
On Tue, Jul 03, 2018 at 11:15:21AM +, Gaoming (ming, consumer BG) wrote:
>
> You misunderstand my question. Why was the choice of a blocksize of
> 1024 made?
>
> -some one choose, not me . I guess they want get more inodes in 20M
> filesystem.
That can't be the explanation.
I just
: [PATCH] ext4: e2fsprogs: fix inode bitmap num
not integer,incompatible for ancient android devices
On Tue, Jul 03, 2018 at 12:58:48AM +, Gaoming (ming, consumer BG) wrote:
> And can you help me understand *why* such a choice was made?
> -if there is such a problem in your device
: [PATCH] ext4: e2fsprogs: fix inode bitmap num
not integer,incompatible for ancient android devices
On Tue, Jul 03, 2018 at 12:58:48AM +, Gaoming (ming, consumer BG) wrote:
> And can you help me understand *why* such a choice was made?
> -if there is such a problem in your device
On Tue, Jul 03, 2018 at 12:58:48AM +, Gaoming (ming, consumer BG) wrote:
> 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.
You
On Tue, Jul 03, 2018 at 12:58:48AM +, Gaoming (ming, consumer BG) wrote:
> 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.
You
: Gaoming (ming, consumer BG)
抄送: linux-e...@vger.kernel.org; linux-kernel@vger.kernel.org; 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
: Gaoming (ming, consumer BG)
抄送: linux-e...@vger.kernel.org; linux-kernel@vger.kernel.org; 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 +, 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
On Mon, Jul 02, 2018 at 09:34:28AM +, 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
21:04
收件人: Gaoming (ming, consumer BG)
抄送: linux-e...@vger.kernel.org; linux-kernel@vger.kernel.org; Liqingchao
(sorp); Shenchen (harry); miaoxie (A); yangfei (D); Renlipeng (OS driver)
主题: Re: 答复: 答复: 答复: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not
integer,incompatible for ancient
21:04
收件人: Gaoming (ming, consumer BG)
抄送: linux-e...@vger.kernel.org; linux-kernel@vger.kernel.org; Liqingchao
(sorp); Shenchen (harry); miaoxie (A); yangfei (D); Renlipeng (OS driver)
主题: Re: 答复: 答复: 答复: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not
integer,incompatible for ancient
On Sat, Jun 30, 2018 at 01:26:43AM +, Gaoming (ming, consumer BG) wrote:
> Yes, it is caused by using 1024 blocksize.
> It is historical problem, and I have to admit that's not good idea. I don't
> know why somebody choose it some years before.
> It has been corrected two years before or
On Sat, Jun 30, 2018 at 01:26:43AM +, Gaoming (ming, consumer BG) wrote:
> Yes, it is caused by using 1024 blocksize.
> It is historical problem, and I have to admit that's not good idea. I don't
> know why somebody choose it some years before.
> It has been corrected two years before or
...@vger.kernel.org; linux-kernel@vger.kernel.org; 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 Fri, Jun 29, 2018 at 02:06:03AM +, Gaoming (ming
...@vger.kernel.org; linux-kernel@vger.kernel.org; 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 Fri, Jun 29, 2018 at 02:06:03AM +, Gaoming (ming
On Fri, Jun 29, 2018 at 02:06:03AM +, Gaoming (ming, consumer BG) wrote:
> We use usual inode size, it is 256 bytes.
>
> Yes, this commit is in my repository.
> But there is a bug in this patch.
>
> Let me show you,
> Here is the bug: " return ALIGN(inodes, (info.block_size /
On Fri, Jun 29, 2018 at 02:06:03AM +, Gaoming (ming, consumer BG) wrote:
> We use usual inode size, it is 256 bytes.
>
> Yes, this commit is in my repository.
> But there is a bug in this patch.
>
> Let me show you,
> Here is the bug: " return ALIGN(inodes, (info.block_size /
答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not
integer,incompatible for ancient android devices
On Thu, Jun 28, 2018 at 07:56:59AM +, Gaoming (ming, consumer BG) wrote:
> You see, Inodes per group is 1708,which is illegal as you said.
>
> So, the problem exists a long time
答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not
integer,incompatible for ancient android devices
On Thu, Jun 28, 2018 at 07:56:59AM +, Gaoming (ming, consumer BG) wrote:
> You see, Inodes per group is 1708,which is illegal as you said.
>
> So, the problem exists a long time
On Thu, Jun 28, 2018 at 07:56:59AM +, Gaoming (ming, consumer BG) wrote:
> You see, Inodes per group is 1708,which is illegal as you said.
>
> So, the problem exists a long time until Jun 21th 2018.
>
> You complained the problem in 2011, they do not fix it till 2018.
> Just as
> I
On Thu, Jun 28, 2018 at 07:56:59AM +, Gaoming (ming, consumer BG) wrote:
> You see, Inodes per group is 1708,which is illegal as you said.
>
> So, the problem exists a long time until Jun 21th 2018.
>
> You complained the problem in 2011, they do not fix it till 2018.
> Just as
> I
答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not
integer,incompatible for ancient android devices
On Thu, Jun 28, 2018 at 01:40:30AM +, Gaoming (ming, consumer BG) wrote:
> Hi tytso,
>
> I have checked that make_ext4fs code was deleted o Jun 21th 2018 on master
> branch of /sys
答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not
integer,incompatible for ancient android devices
On Thu, Jun 28, 2018 at 01:40:30AM +, Gaoming (ming, consumer BG) wrote:
> Hi tytso,
>
> I have checked that make_ext4fs code was deleted o Jun 21th 2018 on master
> branch of /sys
On Thu, Jun 28, 2018 at 01:40:30AM +, Gaoming (ming, consumer BG) wrote:
> Hi tytso,
>
> I have checked that make_ext4fs code was deleted o Jun 21th 2018 on master
> branch of /system/extras repository.
> e.g.
> https://android-review.googlesource.com/c/platform/system/extras/+/708003
On Thu, Jun 28, 2018 at 01:40:30AM +, Gaoming (ming, consumer BG) wrote:
> Hi tytso,
>
> I have checked that make_ext4fs code was deleted o Jun 21th 2018 on master
> branch of /system/extras repository.
> e.g.
> https://android-review.googlesource.com/c/platform/system/extras/+/708003
Hi tytso,
I have checked that make_ext4fs code was deleted o Jun 21th 2018 on master
branch of /system/extras repository.
e.g.
https://android-review.googlesource.com/c/platform/system/extras/+/708003
that means this tools has been widely used along serval years.
And it is probably that many
Hi tytso,
I have checked that make_ext4fs code was deleted o Jun 21th 2018 on master
branch of /system/extras repository.
e.g.
https://android-review.googlesource.com/c/platform/system/extras/+/708003
that means this tools has been widely used along serval years.
And it is probably that many
30 matches
Mail list logo
