From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from b.ns.miles-group.at ([95.130.255.144] helo=radon.swed.at) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1VPXz8-0003JI-JP for linux-mtd@lists.infradead.org; Fri, 27 Sep 2013 13:21:34 +0000 Message-ID: <52458644.5040900@nod.at> Date: Fri, 27 Sep 2013 15:21:08 +0200 From: Richard Weinberger MIME-Version: 1.0 To: Richard Genoud Subject: Re: [PATCH] UBI: fastmap: fix backward compatibility with image_seq References: <1380286316-29911-1-git-send-email-richard.genoud@gmail.com> <52458377.7040100@nod.at> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: linux-mtd , David Woodhouse , "linux-kernel@vger.kernel.org" , Artem Bityutskiy List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Am 27.09.2013 15:16, schrieb Richard Genoud: > 2013/9/27 Richard Weinberger : >> Am 27.09.2013 14:51, schrieb Richard Genoud: >>> Some old UBI implementations (e.g. U-Boot) have not implemented the image >>> sequence feature. >>> So, when erase blocks are written, the image sequence in the ec header >>> is lost (set to zero). >>> UBI scan_all() takes this case into account (commits >>> 32bc4820287a1a03982979515949e8ea56eac641 and >>> 2eadaad67b2b6bd132eda105128d2d466298b8e3) >>> >>> But fastmap scan functions (ubi_scan_fastmap() and scan_pool()) didn't. >>> >>> This patch fixes the issue. >>> >>> Signed-off-by: Richard Genoud >>> --- >> >> W00t! Good catch! >> >> Acked-by: Richard Weinberger > Thanks :) > > > There's still an error when the image sequence is bad: > [ 35.632812] UBI error: scan_pool: bad image seq: 0x0, expected: 0x6e452f03 > [ 35.640625] UBI error: ubi_scan_fastmap: Attach by fastmap failed, > doing a full scan! > [ 35.648437] kmem_cache_destroy ubi_ainf_peb_slab: Slab cache still > has objects <- the destroy_ai in line 1415 *grrr*, the problem here is that not all allocations which are done via kmem_cache_alloc(ai->aeb_slab_cache, ...) got kfree()'d. Thanks, //richard