[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180628022900.GA663@thunk.org>
Date: Wed, 27 Jun 2018 22:29:00 -0400
From: "Theodore Y. Ts'o" <tytso@....edu>
To: "Gaoming (ming, consumer BG)" <gaoming20@...wei.com>
Cc: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Liqingchao (sorp)" <sorp.liqingchao@...wei.com>,
"Shenchen (harry)" <harry.shen@...wei.com>,
"miaoxie (A)" <miaoxie@...wei.com>,
"yangfei (D)" <yangfei39@...wei.com>
Subject: Re: 答复: [PATCH] ext4: e2fsprogs: fix inode bitmap num not
integer,incompatible for ancient android devices
On Thu, Jun 28, 2018 at 01:40:30AM +0000, 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
Make_ext4fs was fixed not create invalid file systems a *long* time
ago. What I'm not sure about is why the patch hasn't gotten out to
more Android manufacters sooner.
It should have been fixed by sometime in 2012 --- I complained to the
Android team in early 2011. What I don't understand is why people are
coming out of the woodwork *now*.
- Ted
Powered by blists - more mailing lists