All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: akpm@linux-foundation.org
Cc: torvalds@linux-foundation.org, xemul@openvz.org,
	linux-arch@vger.kernel.org, randy.dunlap@oracle.com,
	Kyle McMartin <kyle@mcmartin.ca>
Subject: Re: [patch 041/234] Report that kernel is tainted if there was an OOPS
Date: Tue, 17 Jul 2007 05:42:48 -0600	[thread overview]
Message-ID: <20070717114248.GA14791@parisc-linux.org> (raw)
In-Reply-To: <200707171103.l6HB3gDf013411@imap1.linux-foundation.org>

On Tue, Jul 17, 2007 at 04:03:42AM -0700, akpm@linux-foundation.org wrote:
> From: Pavel Emelianov <xemul@openvz.org>
> 
> If the kernel OOPSed or BUGed then it probably should be considered as
> tainted.  Thus, all subsequent OOPSes and SysRq dumps will report the
> tainted kernel.  This saves a lot of time explaining oddities in the
> calltraces.

Any reason parisc is missing?

diff --git a/arch/parisc/kernel/traps.c b/arch/parisc/kernel/traps.c
index c3ec9f1..07a4e7b 100644
--- a/arch/parisc/kernel/traps.c
+++ b/arch/parisc/kernel/traps.c
@@ -264,6 +264,7 @@ KERN_CRIT "                     ||     ||\n");
 
 	show_regs(regs);
 	dump_stack();
+	add_taint(TAINT_DIE);
 
 	if (in_interrupt())
 		panic("Fatal exception in interrupt");

-- 
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2007-07-17 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 11:03 [patch 041/234] Report that kernel is tainted if there was an OOPS akpm
2007-07-17 11:42 ` Matthew Wilcox [this message]
2007-07-17 18:10 ` Russell King
2007-07-18  5:29   ` Pavel Emelianov
2007-07-18  7:16     ` Russell King
2007-07-18  7:22       ` Pavel Emelianov
2007-07-18  7:28         ` Russell King
2007-07-18 18:40           ` H. Peter Anvin

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=20070717114248.GA14791@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=akpm@linux-foundation.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-arch@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=torvalds@linux-foundation.org \
    --cc=xemul@openvz.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 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.