From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754769Ab1BJDFr (ORCPT ); Wed, 9 Feb 2011 22:05:47 -0500 Received: from mx1.redhat.com ([209.132.183.28]:29905 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753892Ab1BJDFp (ORCPT ); Wed, 9 Feb 2011 22:05:45 -0500 Message-ID: <4D5355D1.3050408@redhat.com> Date: Thu, 10 Feb 2011 11:04:49 +0800 From: Cong Wang User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7 MIME-Version: 1.0 To: "Eric W. Biederman" CC: Seiji Aguchi , "hpa@zytor.com" , "andi@firstfloor.org" , "bp@alien8.de" , "seto.hidetoshi@jp.fujitsu.com" , "gregkh@suse.de" , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "x86@kernel.org" , "dle-develop@lists.sourceforge.net" , Satoru Moriya Subject: Re: [RFC][PATCH v2] Controlling kexec behaviour when hardware error happened. References: <5C4C569E8A4B9B42A84A977CF070A35B2C1494DBE0@USINDEVS01.corp.hds.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 于 2011年02月10日 01:07, Eric W. Biederman 写道: > > 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail191.messagelabs.com (mail191.messagelabs.com [216.82.242.19]) by kanga.kvack.org (Postfix) with SMTP id 2FCB88D0039 for ; Wed, 9 Feb 2011 22:05:38 -0500 (EST) Message-ID: <4D5355D1.3050408@redhat.com> Date: Thu, 10 Feb 2011 11:04:49 +0800 From: Cong Wang MIME-Version: 1.0 Subject: Re: [RFC][PATCH v2] Controlling kexec behaviour when hardware error happened. References: <5C4C569E8A4B9B42A84A977CF070A35B2C1494DBE0@USINDEVS01.corp.hds.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-linux-mm@kvack.org List-ID: To: "Eric W. Biederman" Cc: Seiji Aguchi , "hpa@zytor.com" , "andi@firstfloor.org" , "bp@alien8.de" , "seto.hidetoshi@jp.fujitsu.com" , "gregkh@suse.de" , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "x86@kernel.org" , "dle-develop@lists.sourceforge.net" , Satoru Moriya 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: email@kvack.org