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

Message-ID: <CACTFLANAFT=G4kFvHUqvLrt=MxgpJnJ-EeHY8zd49pZvsNRejw@mail.gmail.com>
Date:	Tue, 19 Jul 2011 15:57:06 +0200
From:	Daniel Mack <zonque@...il.com>
To:	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc:	Sven Neumann <s.neumann@...mfeld.com>,
	Artem Bityutskiy <dedekind1@...il.com>,
	Adrian Hunter <adrian.hunter@...ia.com>
Subject: Regression in handling of unsafe UBI shutdown

Hey,

we're facing a new behaviour with 3.0-rc7 kernels wrt UBI file systems
that are not properly unmounted on shut down. The newest kernel we're
using in production is 2.6.36.4, and this version doesn't show the
effect.

When our devices boot up, the bootloader (U-Boot) initializes its UBI
code, reads in the uImage from the root partition and executes it.
This worked very well in thousands of installations previously (with
kernels up to version 2.6.36.4), and generally, it still does work
well with the latest cutting edge when the kernel is shut down
properly and unmounts the UBI partitions safely. However, if the power
is removed out of a sudden from a running system, U-Boot now doesn't
like the FS anymore upon the next boot:

Creating 1 MTD partitions on "nand0":
0x00120000-0x08000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            126 MiB
UBI: number of good PEBs:        1014
UBI: number of bad PEBs:         1
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     2
UBI: available PEBs:             8
UBI: total number of reserved PEBs: 1006
UBI: number of PEBs reserved for bad PEB handling: 10
UBI: max/mean erase counter: 4/3
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?

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/