From: Harald Hoyer <harald.hoyer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH v4] Let user specify the action after fail
Date: Tue, 09 Apr 2013 11:15:54 +0200 [thread overview]
Message-ID: <5163DC4A.7060107@gmail.com> (raw)
In-Reply-To: <30ace4e3dce0dbe9b75572e533d2084ce7c26977.1364553259.git.bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Am 29.03.2013 11:36, schrieb Baoquan He:
> Currently the default action is emergency_shell when failure happened
> during system boot. In kdump, this default may not be expected. E.g,
> if dump target is not rootfs, it does not matter if mount root failed.
> Adding an action which allow dracut always go ahead though failure
> happens is needed by kdump.
>
> So here add a function action_on_fail() and cmdline parameter
> action_on_fail=<shell | continue>. Use action_to_fail() to replace
> emergency_shell which was called after failure. By $(getarg action_on_fail=),
> decide to drop into shell, or to leave away the failure and go ahead.
>
> v3->v4:
> add handling of selinux policy loaded failure, and change code format to
> be consitent
>
> Signed-off-by: Baoquan He <bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
applied and slightly edited
prev parent reply other threads:[~2013-04-09 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 10:36 [PATCH v4] Let user specify the action after fail Baoquan He
[not found] ` <30ace4e3dce0dbe9b75572e533d2084ce7c26977.1364553259.git.bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-04-08 6:40 ` Dave Young
2013-04-09 9:15 ` Harald Hoyer [this message]
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=5163DC4A.7060107@gmail.com \
--to=harald.hoyer-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=bhe-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.