All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: oomichi@mxs.nes.nec.co.jp, "Luck, Tony" <tony.luck@intel.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	tachibana@mxm.nes.nec.co.jp, Andi Kleen <andi@firstfloor.org>,
	Borislav Petkov <bp@alien8.de>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	anderson@redhat.com, "K.Prasad" <prasad@linux.vnet.ibm.com>,
	crash-utility@redhat.com
Subject: Re: [Patch 1/4][kernel][slimdump] Add new elf-note of type NT_NOCOREDUMP to capture slimdump
Date: Wed, 5 Oct 2011 13:13:08 -0400	[thread overview]
Message-ID: <20111005171308.GG30146@redhat.com> (raw)
In-Reply-To: <10327.1317830438@turing-police.cc.vt.edu>

On Wed, Oct 05, 2011 at 12:00:38PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 05 Oct 2011 11:52:17 EDT, Vivek Goyal said:
> 
> > I am assuming that basic MCE error messages are available in kernel log. 
> 
> They're not in the kernel log if it's an MCE that causes the kernel to declare
> a panic. There's some MCE's that you can retry the operation and continue, and
> some that you can get away with poisoning a page, killing the process, and rest
> of the system is OK.  But some you really need to roll over and die because you
> can't guarantee kernel integrity anymore.
> 
> And at that point, those messages are never gonna make it to syslogd and onto
> disk.

Actually I meant that these messages should have made into kernel log
buffer and not on disk. And user space has capability to just extract
kernel log buffer by looking at /proc/vmcore.

Thanks
Vivek

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

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: "K.Prasad" <prasad@linux.vnet.ibm.com>,
	Borislav Petkov <bp@alien8.de>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org, crash-utility@redhat.com,
	kexec@lists.infradead.org, Andi Kleen <andi@firstfloor.org>,
	"Luck, Tony" <tony.luck@intel.com>,
	anderson@redhat.com, tachibana@mxm.nes.nec.co.jp,
	oomichi@mxs.nes.nec.co.jp
Subject: Re: [Patch 1/4][kernel][slimdump] Add new elf-note of type NT_NOCOREDUMP to capture slimdump
Date: Wed, 5 Oct 2011 13:13:08 -0400	[thread overview]
Message-ID: <20111005171308.GG30146@redhat.com> (raw)
In-Reply-To: <10327.1317830438@turing-police.cc.vt.edu>

On Wed, Oct 05, 2011 at 12:00:38PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 05 Oct 2011 11:52:17 EDT, Vivek Goyal said:
> 
> > I am assuming that basic MCE error messages are available in kernel log. 
> 
> They're not in the kernel log if it's an MCE that causes the kernel to declare
> a panic. There's some MCE's that you can retry the operation and continue, and
> some that you can get away with poisoning a page, killing the process, and rest
> of the system is OK.  But some you really need to roll over and die because you
> can't guarantee kernel integrity anymore.
> 
> And at that point, those messages are never gonna make it to syslogd and onto
> disk.

Actually I meant that these messages should have made into kernel log
buffer and not on disk. And user space has capability to just extract
kernel log buffer by looking at /proc/vmcore.

Thanks
Vivek

  parent reply	other threads:[~2011-10-05 17:13 UTC|newest]

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03  7:07 [Patch 0/4] Slimdump framework using NT_NOCOREDUMP elf-note K.Prasad
2011-10-03  7:07 ` K.Prasad
2011-10-03  7:32 ` [Patch 1/4][kernel][slimdump] Add new elf-note of type NT_NOCOREDUMP to capture slimdump K.Prasad
2011-10-03  7:32   ` K.Prasad
2011-10-03 10:10   ` Eric W. Biederman
2011-10-03 10:10     ` Eric W. Biederman
2011-10-03 12:03     ` K.Prasad
2011-10-03 12:03       ` K.Prasad
2011-10-04  6:34       ` Borislav Petkov
2011-10-04  6:34         ` Borislav Petkov
2011-10-05  7:07         ` K.Prasad
2011-10-05  7:07           ` K.Prasad
2011-10-05  7:31           ` Borislav Petkov
2011-10-05  7:31             ` Borislav Petkov
2011-10-05  9:47             ` K.Prasad
2011-10-05  9:47               ` K.Prasad
2011-10-05 12:41               ` Borislav Petkov
2011-10-05 12:41                 ` Borislav Petkov
2011-10-05 15:52               ` Vivek Goyal
2011-10-05 15:52                 ` Vivek Goyal
2011-10-05 16:00                 ` Valdis.Kletnieks
2011-10-05 16:16                   ` Borislav Petkov
2011-10-05 16:16                     ` Borislav Petkov
2011-10-05 17:20                     ` Vivek Goyal
2011-10-05 17:20                       ` Vivek Goyal
2011-10-05 17:13                   ` Vivek Goyal [this message]
2011-10-05 17:13                     ` Vivek Goyal
2011-10-05 11:55             ` Valdis.Kletnieks
2011-10-05 12:31               ` Borislav Petkov
2011-10-05 12:31                 ` Borislav Petkov
2011-10-05 15:19           ` Vivek Goyal
2011-10-05 15:19             ` Vivek Goyal
2011-10-05 15:30           ` Vivek Goyal
2011-10-05 15:30             ` Vivek Goyal
2011-10-03 22:53     ` Luck, Tony
2011-10-03 22:53       ` Luck, Tony
2011-10-04 14:04   ` Vivek Goyal
2011-10-04 14:04     ` Vivek Goyal
2011-10-05  7:18     ` K.Prasad
2011-10-05  7:18       ` K.Prasad
2011-10-05  7:33       ` Borislav Petkov
2011-10-05  7:33         ` Borislav Petkov
2011-10-05  9:23         ` K.Prasad
2011-10-05  9:23           ` K.Prasad
2011-10-05 15:25       ` Vivek Goyal
2011-10-05 15:25         ` Vivek Goyal
2011-10-07 16:12         ` K.Prasad
2011-10-07 16:12           ` K.Prasad
2011-10-10  7:07           ` Borislav Petkov
2011-10-10  7:07             ` Borislav Petkov
2011-10-11 18:44             ` K.Prasad
2011-10-11 18:44               ` K.Prasad
2011-10-11 18:59               ` Luck, Tony
2011-10-11 18:59                 ` Luck, Tony
2011-10-12  0:20               ` Andi Kleen
2011-10-12  0:20                 ` Andi Kleen
2011-10-12 10:44               ` Borislav Petkov
2011-10-12 10:44                 ` Borislav Petkov
2011-10-12 15:59                 ` Vivek Goyal
2011-10-12 15:59                   ` Vivek Goyal
2011-10-12 15:51               ` Vivek Goyal
2011-10-12 15:51                 ` Vivek Goyal
2011-10-14 11:30                 ` K.Prasad
2011-10-14 11:30                   ` K.Prasad
2011-10-14 14:14                   ` Vivek Goyal
2011-10-14 14:14                     ` Vivek Goyal
2011-10-18 17:41                     ` K.Prasad
2011-10-18 17:41                       ` K.Prasad
2011-10-11 18:55             ` Luck, Tony
2011-10-04 14:30   ` Vivek Goyal
2011-10-04 14:30     ` Vivek Goyal
2011-10-05  7:41     ` K.Prasad
2011-10-05  7:41       ` K.Prasad
2011-10-05 15:40       ` Vivek Goyal
2011-10-05 15:40         ` Vivek Goyal
2011-10-05 15:58         ` Luck, Tony
2011-10-05 16:25           ` Borislav Petkov
2011-10-05 16:25             ` Borislav Petkov
2011-10-05 17:10           ` Vivek Goyal
2011-10-05 17:10             ` Vivek Goyal
2011-10-05 17:20             ` Borislav Petkov
2011-10-05 17:20               ` Borislav Petkov
2011-10-05 17:29               ` Vivek Goyal
2011-10-05 17:29                 ` Vivek Goyal
2011-10-05 17:43                 ` Borislav Petkov
2011-10-05 17:43                   ` Borislav Petkov
2011-10-05 18:00                 ` Dave Anderson
2011-10-05 18:00                   ` Dave Anderson
2011-10-05 18:09                   ` Vivek Goyal
2011-10-05 18:09                     ` Vivek Goyal
2011-10-04 15:04   ` Nick Bowler
2011-10-04 15:04     ` Nick Bowler
2011-10-07 16:36     ` K.Prasad
2011-10-07 16:36       ` K.Prasad
2011-10-07 18:19       ` Nick Bowler
2011-10-07 18:19         ` Nick Bowler
2011-10-03  7:35 ` [Patch 2/4][kexec-tools] Recognise NT_NOCOREDUMP elf-note type K.Prasad
2011-10-03  7:35   ` K.Prasad
2011-10-03  7:37 ` [Patch 3/4][makedumpfile] Capture slimdump if elf-note NT_NOCOREDUMP present K.Prasad
2011-10-03  7:37   ` K.Prasad
2011-10-03  7:45 ` [Patch 4/4][crash] Recognise elf-note of type NT_NOCOREDUMP before vmcore analysis K.Prasad
2011-10-03  7:45   ` K.Prasad

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=20111005171308.GG30146@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=anderson@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=bp@alien8.de \
    --cc=crash-utility@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oomichi@mxs.nes.nec.co.jp \
    --cc=prasad@linux.vnet.ibm.com \
    --cc=tachibana@mxm.nes.nec.co.jp \
    --cc=tony.luck@intel.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 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.