linux-kernel - Re: Regression in handling of unsafe UBI shutdown

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 24 Jul 2011 16:52:30 +0200
From:	Daniel Mack <zonque@...il.com>
To:	Mike Hench <mhench@...tions.com>
Cc:	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Adrian Hunter <adrian.hunter@...ia.com>,
	Sven Neumann <s.neumann@...mfeld.com>,
	Artem Bityutskiy <dedekind1@...il.com>
Subject: Re: Regression in handling of unsafe UBI shutdown

On Wed, Jul 20, 2011 at 1:45 PM, Mike Hench <mhench@...tions.com> wrote:
>> UBIFS: recovery needed
>> Error reading superblock on volume 'ubi:RootFS'!
>> UBIFS not mounted, use ubifs mount to mount volume first!
>> Wrong Image Format for bootm command
>> ERROR: can't get kernel image!
>
>
> Be nice to know what error.
> FWIW:
> a) I do not see this. I have very limited experience with 3.0-rc7 though
> so maybe I should not say anything :-)
>
> b) sometimes UBIFS decides to do recovery in u-boot, sometimes not.
> it seems to depend on the type of content in the journal.
> Lots of deleted files seem to trigger u-boot to perform a recovery for
> instance.
> I was running out of memory In u-boot while replaying the journal
> at one point with an older kernel. This produced the same top level
> error.

Thank you very much vor mentioning this, as it totally pointed me in
the right direction. Whatever really caused it, we ended up with
larger journal produced by newer kernels in comparison to older ones,
and U-Boot indeed ran out memory when trying to access the FS later.
Increasing the amount of available memory in U-Boot fixes the problem
for us.

Sorry for scaring you, but it looked like a major regression in the
first place. And thanks again to everyone for helping sort this out.


Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/