From: Pavel Machek <pavel@ucw.cz>
To: Vishnu Pratap Singh <vishnu.ps@samsung.com>
Cc: paul.gortmaker@windriver.com, snitzer@redhat.com,
dehrenberg@chromium.org, akpm@linux-foundation.org,
mszeredi@suse.cz, linux-kernel@vger.kernel.org, cpgs@samsung.com
Subject: Re: [PATCH] init/do_mounts: Add create_dev() failure log
Date: Tue, 26 May 2015 08:25:34 +0200 [thread overview]
Message-ID: <20150526062534.GA11401@amd> (raw)
In-Reply-To: <1432561783-3317-1-git-send-email-vishnu.ps@samsung.com>
On Mon 2015-05-25 19:19:43, Vishnu Pratap Singh wrote:
> if create_dev() function fails to create the root mount device (/dev/root),
> then it goes to panic as root device not found but there is no check/log
> present in case of failure, So i have added the log in case it fails to create
> the root device. It will help in debugging.
>
> Signed-off-by: Vishnu Pratap Singh <vishnu.ps@samsung.com>
> ---
> init/do_mounts.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/init/do_mounts.c b/init/do_mounts.c
> index 8369ffa..a68aaf6 100644
> --- a/init/do_mounts.c
> +++ b/init/do_mounts.c
> @@ -532,7 +532,8 @@ void __init mount_root(void)
> }
> #endif
> #ifdef CONFIG_BLOCK
> - create_dev("/dev/root", ROOT_DEV);
> + if(create_dev("/dev/root", ROOT_DEV) < 0)
> + printk(KERN_ERR "Failed to create %s device !!\n", "/dev/root");
No change, AFAICT. Please fix stuff I pointed in the email, and you
can get my acked-by ;-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-05-26 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <130285@samsung.com>
2015-05-25 5:17 ` [PATCH] init/do_mounts: Add create_dev() failure log Vishnu Pratap Singh
2015-05-25 12:59 ` Pavel Machek
2015-05-25 13:49 ` Vishnu Pratap Singh
2015-05-26 6:25 ` Pavel Machek [this message]
2015-05-26 6:26 ` [PATCHv2] " Vishnu Pratap Singh
2015-05-26 8:32 ` Pavel Machek
2015-05-27 23:27 ` Andrew Morton
2015-05-22 12:37 [PATCH] " Vishnu Pratap Singh
2015-05-22 16:48 ` Randy Dunlap
2015-05-22 19:44 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150526062534.GA11401@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=cpgs@samsung.com \
--cc=dehrenberg@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=paul.gortmaker@windriver.com \
--cc=snitzer@redhat.com \
--cc=vishnu.ps@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).