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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACTFLAOsEZksaUXrN9KVeXHnSxtY-h8XWiYDyn_OxTLxmeWjeg@mail.gmail.com>
Date:	Wed, 20 Jul 2011 13:50:21 +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

Hi Mike,

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 :-)

Thanks for this information. It's good to know there are similar
setups used by other people. Are you an an ARM as well?

Did you try to cut the power from your device in the middle of full
operation? If would help a lot if you could try this.


> 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.

And my fear is that the possible types of content changed in UBIFS in
a way that the kernel itself would be able to deal with it, but legacy
code (in U-Boot and in our case) wouldn't. That would explain what I'm
seeing.


Thanks,
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/