From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.newsguy.com ([74.209.136.69]) by merlin.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1SdNt3-00009M-6f for linux-mtd@lists.infradead.org; Sat, 09 Jun 2012 15:47:37 +0000 Message-ID: <4FD37014.90109@newsguy.com> Date: Sat, 09 Jun 2012 08:47:32 -0700 From: Mike Dunn MIME-Version: 1.0 To: Shmulik Ladkani Subject: Re: [PATCH] mtd: nand: Properly initialize 'mtd->bitflip_threshold' prior 'scan_bbt()' is invoked References: <20120608182906.57b4844a@halley> In-Reply-To: <20120608182906.57b4844a@halley> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Artem Bityutskiy , Sascha Hauer , linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, Ivan Djelic , David Woodhouse List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 06/08/2012 08:29 AM, Shmulik Ladkani wrote: > As of edbc454 [mtd: driver _read() returns max_bitflips; mtd_read() > returns -EUCLEAN], 'mtd->bitflip_threshold' must be set for mtd devices > having ECC, prior any 'mtd_read()' call. > Otherwise, 'mtd_read()' will falsely return -EUCLEAN. > > Normally, 'mtd->bitflip_threshold' is initialized when the MTD is added. > > However, this is too late for NAND MTDs, as 'scan_bbt()' is invoked > prior the existing initialization of 'mtd->bitflip_threshold'. > > This is a problem since 'scan_bbt()' calls 'mtd_read()', in the case > of a flash-based bad block table. > It resulted in a falsely reported bitflips indication during BBT read, > which lead to constant scrubbing of the flash BBT blocks. > > Initialize 'mtd->bitflip_threshold' to its default value (if not already > set by the driver), prior invocation of 'scan_bbt()'. > Reviewed-by: Mike Dunn (FWIW). Thanks again Shmulik! I do think that the patch to the bad block management code that I sent yesterday should be merged as well. That would also fix the problem, but it is really a separate issue. Currently ecc errors are ignored during the BBT creation for some configurations but not for others (like that of the mxc_nand controller). It looks like an oversight that they are not ignored, and it makes sense to ignore them, since there's not much you can do about them at that time, and the functions higher up the call stack don't try to. Thanks, Mike