Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753775Ab3JRMA5 (ORCPT ); Fri, 18 Oct 2013 08:00:57 -0400 Received: from top.free-electrons.com ([176.31.233.9]:56067 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753721Ab3JRMAz (ORCPT ); Fri, 18 Oct 2013 08:00:55 -0400 From: Michael Opdenacker To: akpm@linux-foundation.org Cc: linux-kernel@vger.kernel.org, linux-embedded@vger.kernel.org, janne.karhunen@gmail.com, geert@linux-m68k.org, Michael Opdenacker Subject: [PATCH v2] init: make init failures more explicit Date: Fri, 18 Oct 2013 14:00:33 +0200 Message-Id: <1382097633-10166-1-git-send-email-michael.opdenacker@free-electrons.com> X-Mailer: git-send-email 1.8.1.2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2624 Lines: 77 This patch proposes to make init failures more explicit. Before this, the "No init found" message didn't help much. It could sometimes be misleading and actually mean "No *working* init found". This message could hide many different issues: - no init program candidates found at all - some init program candidates exist but can't be executed (missing execute permissions, failed to load shared libraries, executable compiled for an unknown architecture...) This patch notifies the kernel user when a candidate init program is found but can't be executed. The error code is displayed, to quickly find the root cause. "No init found" is also replaced by "No working init found", which is more correct. This will help embedded Linux developers (especially the new comers), regularly making and debugging new root filesystems. Signed-off-by: Michael Opdenacker --- init/main.c | 24 +++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/init/main.c b/init/main.c index 63d3e8f..3662767 100644 --- a/init/main.c +++ b/init/main.c @@ -811,6 +811,20 @@ static int run_init_process(const char *init_filename) (const char __user *const __user *)envp_init); } +static int try_to_run_init_process(const char *init_filename) +{ + int ret; + + ret = run_init_process(init_filename); + + if (ret && ret != -ENOENT) { + pr_err("Starting init: %s exists but couldn't execute it (error: %d - see errno-base.h and errno.h)\n", + init_filename, ret); + } + + return ret; +} + static noinline void __init kernel_init_freeable(void); static int __ref kernel_init(void *unused) @@ -843,13 +857,13 @@ static int __ref kernel_init(void *unused) pr_err("Failed to execute %s. Attempting defaults...\n", execute_command); } - if (!run_init_process("/sbin/init") || - !run_init_process("/etc/init") || - !run_init_process("/bin/init") || - !run_init_process("/bin/sh")) + if (!try_to_run_init_process("/sbin/init") || + !try_to_run_init_process("/etc/init") || + !try_to_run_init_process("/bin/init") || + !try_to_run_init_process("/bin/sh")) return 0; - panic("No init found. Try passing init= option to kernel. " + panic("No working init found. Try passing init= option to kernel. " "See Linux Documentation/init.txt for guidance."); } -- 1.8.1.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/