From: Cong Wang <amwang@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Seiji Aguchi <seiji.aguchi@hds.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"andi@firstfloor.org" <andi@firstfloor.org>,
"bp@alien8.de" <bp@alien8.de>,
"seto.hidetoshi@jp.fujitsu.com" <seto.hidetoshi@jp.fujitsu.com>,
"gregkh@suse.de" <gregkh@suse.de>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"x86@kernel.org" <x86@kernel.org>,
"dle-develop@lists.sourceforge.net"
<dle-develop@lists.sourceforge.net>,
Satoru Moriya <satoru.moriya@hds.com>
Subject: Re: [RFC][PATCH v2] Controlling kexec behaviour when hardware error happened.
Date: Thu, 10 Feb 2011 11:04:49 +0800 [thread overview]
Message-ID: <4D5355D1.3050408@redhat.com> (raw)
In-Reply-To: <m1bp2l2l31.fsf@fess.ebiederm.org>
ao? 2011a1'02ae??10ae?JPY 01:07, Eric W. Biederman a??e??:
>
> Is there any reason we can't put logic to decided if we should write
> a crashdump in the crashdump userspace?
>
Doesn't this already provide a choice for the user to decide if he wants
a crashdump via sysctl?
Except some minor issues pointed by you and Greg, this patch looks fine
for me.
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-02-10 3:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 16:35 Seiji Aguchi
2011-02-09 16:51 ` Greg KH
2011-02-09 17:06 ` Eric W. Biederman
2011-02-09 17:07 ` Eric W. Biederman
2011-02-10 3:04 ` Cong Wang [this message]
2011-02-10 8:36 ` Hidetoshi Seto
2011-02-10 9:14 ` Borislav Petkov
2011-02-14 1:20 ` Hidetoshi Seto
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=4D5355D1.3050408@redhat.com \
--to=amwang@redhat.com \
--cc=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=dle-develop@lists.sourceforge.net \
--cc=ebiederm@xmission.com \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=satoru.moriya@hds.com \
--cc=seiji.aguchi@hds.com \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox