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: <1311139283.20738.150.camel@sauron>
Date:	Wed, 20 Jul 2011 08:21:18 +0300
From:	Artem Bityutskiy <dedekind1@...il.com>
To:	Daniel Mack <zonque@...il.com>
Cc:	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org,
	Sven Neumann <s.neumann@...mfeld.com>,
	Adrian Hunter <adrian.hunter@...ia.com>
Subject: Re: Regression in handling of unsafe UBI shutdown

On Tue, 2011-07-19 at 15:57 +0200, Daniel Mack 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!
> 
> 
> Hence my question is: were there any radical changes in the UBI/UBIFS
> code on the kernel side that make older code not like the new content
> anymore?

Daniel, sorry, I have no time to look at this now, could you please try
to bisect the issue?

-- 
Best Regards,
Artem Bityutskiy

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