Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Dave Young <dyoung@redhat.com>,
	kexec@lists.infradead.org, WANG Chao <chaowang@redhat.com>
Subject: Re: [PATCH] kexec, remove panic_on_warn kernel parameter from kdump situations
Date: Fri, 02 Jan 2015 08:07:20 -0500	[thread overview]
Message-ID: <54A69808.4010401@redhat.com> (raw)
In-Reply-To: <20150102125423.GA18785@redhat.com>



On 01/02/2015 07:54 AM, Vivek Goyal wrote:
> On Tue, Dec 30, 2014 at 09:57:51AM -0500, Prarit Bhargava wrote:
>> panic_on_warn kernel parameter will cause the kernel to panic when a
>> WARN() is hit in the kernel.  This is not a good situation for the kdump
>> kernel because then it would be possible for the kdump kernel to panic in
>> a non-fatal WARN().
>>
>> This patch removes panic_on_warn as a kernel parameter for the kdump
>> kernel.
>>
> 
> I think modifying kexec-tools is not best place for this. It probably is better to take care of this in distribution specific scripts.
> 
> In the past we have learnt that it is best that kexec-tools does least
> amount of manipulation with command line.

Well .. here's the question to think about: what does adding panic_on_warn to
the kdump kernel get you?  AFAICT, nothing.

If panic_on_warn is specified, the only thing that will happen is that kdump
will fail (which is always bad IMO).  There is no real difference in the stack
trace between the WARN() and panic situations so there is no information loss.

So I disagree -- we should never specify panic_on_warn on kdump kernel.

P.

> 
> Thanks
> Vivek
> 
>> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
>> Cc: Dave Young <dyoung@redhat.com>
>> Cc: Vivek Goyal <vgoyal@redhat.com>
>> Cc: WANG Chao <chaowang@redhat.com>
>> ---
>>  kexec/kexec.c |    4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/kexec/kexec.c b/kexec/kexec.c
>> index b088916..323cafb 100644
>> --- a/kexec/kexec.c
>> +++ b/kexec/kexec.c
>> @@ -1048,8 +1048,10 @@ char *get_command_line(void)
>>  	line[strlen(line) - 1] = '\0';
>>  
>>  	remove_parameter(line, "BOOT_IMAGE");
>> -	if (kexec_flags & KEXEC_ON_CRASH)
>> +	if (kexec_flags & KEXEC_ON_CRASH) {
>>  		remove_parameter(line, "crashkernel");
>> +		remove_parameter(line, "panic_on_warn");
>> +	}
>>  
>>  	return line;
>>  }
>> -- 
>> 1.7.9.3

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2015-01-02 13:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 14:57 [PATCH] kexec, remove panic_on_warn kernel parameter from kdump situations Prarit Bhargava
2015-01-02 12:54 ` Vivek Goyal
2015-01-02 13:07   ` Prarit Bhargava [this message]
2015-01-02 13:17     ` Vivek Goyal
2015-01-05  1:49       ` Simon Horman
2015-01-06  1:44       ` Dave Young
2015-01-06  1:54         ` Vivek Goyal
2015-01-06  8:05           ` Dave Young
2015-01-06 12:46             ` Baoquan He
2015-01-06 13:07               ` Vivek Goyal
2015-01-06 13:06             ` Vivek Goyal

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=54A69808.4010401@redhat.com \
    --to=prarit@redhat.com \
    --cc=chaowang@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=vgoyal@redhat.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