public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Jingbai Ma <jingbai.ma@hp.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com, kumagai-atsushi@mxc.nes.nec.co.jp,
	hpa@zytor.com, yinghai@kernel.org,
	Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [RFC PATCH 0/5] crash dump bitmap: scan memory pages in kernel to speedup kernel dump process
Date: Tue, 12 Mar 2013 12:48:07 -0700	[thread overview]
Message-ID: <87sj408knc.fsf@xmission.com> (raw)
In-Reply-To: <513EFDD6.806@hp.com> (Jingbai Ma's message of "Tue, 12 Mar 2013 18:05:10 +0800")

Jingbai Ma <jingbai.ma@hp.com> writes:

> On 03/11/2013 05:42 PM, Eric W. Biederman wrote:

>> The kernel is known bad.  What is bad is unclear.
>> Executing any extra code is a bad idea.
>>
>> The history here is that before kexec-on-panic there were lots of dump
>> routines that did all of the crashdump logic in the kernel before they
>> shutdown.  They all worked beautifully during development, and on
>> developers test machines and were absolutely worthless in real world
>> situations.
>
> I also have learned some from the old style kernel dump. Yes, they do have some
> problems in real world situations. The primary problems come from I/O operations
> (disk writing/network sending) and invalid page table.

That and they provide no guarantee that you won't write corrupt data.

The kdump based solutions fail safe.  The worst that will happen is that
you don't take a crash dump.  There is no chance of corrupting your
system.


>> A piece of code that walks all of the page tables is most definitely
>> opening itself up to all kinds of failure situations I can't even
>> imagine.
>
> Agree, invalid page table will cause disaster.
> But even in the capture kernel with user space program, it may only causes a
> core dump, user still have chance to dump the crashed system by themselves with
> some special tools, It's possible, but should be very rare in real world.
> I doubt how many users be able to handle it in such kind of situations.
> So in most cases, if page tables have corrupted, and can not dump it normally,
> user would like to reboot the system directly.

For whatever it is worth corrupted page tables.  Or at least page tables
that the cpu thinks are invalid are one of the crash scenarios that I
have seen in the wild on enough occasions to remember them.

Eric


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

  reply	other threads:[~2013-03-12 19:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07 14:58 [RFC PATCH 0/5] crash dump bitmap: scan memory pages in kernel to speedup kernel dump process Jingbai Ma
2013-03-07 14:58 ` [RFC PATCH 1/5] crash dump bitmap: add a kernel config and help document Jingbai Ma
2013-03-07 14:58 ` [RFC PATCH 2/5] crash dump bitmap: init crash dump bitmap in kernel booting process Jingbai Ma
2013-03-07 14:58 ` [RFC PATCH 3/5] crash dump bitmap: scan memory pages in kernel crash process Jingbai Ma
2013-03-07 14:59 ` [RFC PATCH 4/5] crash dump bitmap: add a proc interface for crash dump bitmap Jingbai Ma
2013-03-07 14:59 ` [RFC PATCH 5/5] crash dump bitmap: workaround for kernel 3.9-rc1 kdump issue Jingbai Ma
2013-03-07 15:21 ` [RFC PATCH 0/5] crash dump bitmap: scan memory pages in kernel to speedup kernel dump process Vivek Goyal
2013-03-07 21:38   ` Yinghai Lu
2013-03-07 21:54   ` Eric W. Biederman
2013-03-08 15:52     ` Vivek Goyal
2013-03-08 16:19       ` Eric W. Biederman
2013-03-11  8:18       ` Jingbai Ma
2013-03-11  9:42         ` Eric W. Biederman
2013-03-12 10:05           ` Jingbai Ma
2013-03-12 19:48             ` Eric W. Biederman [this message]
2013-03-08  1:31   ` HATAYAMA Daisuke
2013-03-08 10:06   ` Jingbai Ma
2013-03-08 10:33     ` H. Peter Anvin
2013-03-08 13:31       ` Ma, Jingbai (Kingboard)
2013-03-08 16:13         ` Eric W. Biederman
2013-03-11  8:31           ` Jingbai Ma
2013-03-08 16:19     ` Vivek Goyal
2013-03-11  8:53       ` Jingbai Ma
2013-03-09  4:31     ` HATAYAMA Daisuke
2013-03-11  9:02       ` Jingbai Ma
2013-03-08 10:16   ` Jingbai Ma
  -- strict thread matches above, loose matches on Subject: below --
2013-03-07 14:00 Jingbai Ma

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=87sj408knc.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=jingbai.ma@hp.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=vgoyal@redhat.com \
    --cc=yinghai@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