| Message ID | 1366681216-17378-1-git-send-email-vapier@gentoo.org |
|---|---|
| State | Accepted |
| Commit | 1557b9e1cb669f90696c863fbf525a1033022c10 |
| Headers | show |
On Mon, 2013-04-22 at 21:40 -0400, Mike Frysinger wrote: > 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. Pushed to linux-ubi.git, thanks!
diff --git a/drivers/mtd/ubi/build.c b/drivers/mtd/ubi/build.c index eaa2d4e..474bc89 100644 --- a/drivers/mtd/ubi/build.c +++ b/drivers/mtd/ubi/build.c @@ -1261,7 +1261,11 @@ static int __init ubi_init(void) mtd = open_mtd_device(p->name); if (IS_ERR(mtd)) { err = PTR_ERR(mtd); - goto out_detach; + 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);
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> --- drivers/mtd/ubi/build.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)