From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga11.intel.com ([192.55.52.93]) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZTlJI-0004mf-8R for linux-mtd@lists.infradead.org; Mon, 24 Aug 2015 06:32:48 +0000 Message-ID: <1440397943.15510.2.camel@gmail.com> Subject: Re: [PATCH] mkfs.ubifs: remove the check for UBIFS_MAX_LEB_SZ From: Artem Bityutskiy Reply-To: dedekind1@gmail.com To: Dongsheng Yang , richard.weinberger@gmail.com, computersforpeace@gmail.com Cc: linux-mtd@lists.infradead.org Date: Mon, 24 Aug 2015 09:32:23 +0300 In-Reply-To: <55DA6E69.8070301@cn.fujitsu.com> References: <1439873555-5352-1-git-send-email-yangds.fnst@cn.fujitsu.com> <1439887948.31419.118.camel@gmail.com> <55DA6E69.8070301@cn.fujitsu.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2015-08-24 at 09:07 +0800, Dongsheng Yang wrote: > On 08/18/2015 04:52 PM, Artem Bityutskiy wrote: > > On Tue, 2015-08-18 at 12:52 +0800, Dongsheng Yang wrote: > > > There is a commit 92ed6c0 to increase UBIFS_MAX_LEB_SZ > > > to 2MiB. But recently, as the leb size become larger and > > > larger, 2MiB is not a suitable limit any more. > > > > > > Then remove this check in mkfs.ubifs > > > > > > Signed-off-by: Dongsheng Yang > > > --- > > > NOTE: > > > I am not sure the reason why we have to > > > limit the leb size in mkfs.ubifs. Because > > > I did not find any reason for it, I send > > > this patch out. It's very possible I am > > > mising something. > > > > Well, this is sanity check for the user input. If you accidentally > > added few zeroes, we want to spot this and inform you, and you may > > appreciate that we did not just created a bugus image for you. > > That's > > the idea. > > Sorry, Artem, I was trying to understand it, but I did not got the > point. Could you give me some more information about the idea? Maybe > an example? Well, this is defensive programming concept. Something goes wrong, due to bad user input and/or a bug we get to this place with an bogus size. This check catches it and errors out versus we just go forward, generate a bugus image, which you then flash and find that things do not work, and then spend your time for further investigations. Nothing more than that. Artem.