Commit 1557b9e1 authored Apr 22, 2013 by Mike Frysinger Committed by Artem Bityutskiy May 16, 2013

UBI: do not abort init when ubi.mtd devices cannot be found



The current ubi.mtd parsing logic will warn & continue on when attaching
the specified mtd device fails (for any reason).  It doesn't however skip
things when the specified mtd device can't be opened.

This scenario can be hit in a couple of different ways such as:
 - build NAND controller driver as a module
 - build UBI into the kernel
 - include ubi.mtd on the kernel command line
 - boot the system
 - MTD devices don't exist, so UBI init fails

This is problematic because failing init means the entire UBI layer is
unavailable until you reboot and modify the kernel command line.  If
we just warn and continue on, /dev/ubi_ctrl is available for userland
to add UBI volumes on the fly once it loads the NAND driver.

Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>

parent 6fde0f30

drivers/mtd/ubi/build.c

+5 −1

Original line number	Diff line number	Diff line
		@@ -1261,7 +1261,11 @@ static int __init ubi_init(void)
		mtd = open_mtd_device(p->name);
		if (IS_ERR(mtd)) {
		err = PTR_ERR(mtd);
		ubi_err("cannot open mtd %s, error %d", p->name, err);
		/* See comment below re-ubi_is_module(). */
		if (ubi_is_module())
		goto out_detach;
		continue;
		}

		mutex_lock(&ubi_devices_mutex);

Admin message