From: Randy Dunlap <randy.dunlap@oracle.com>
To: Pavel Emelianov <xemul@sw.ru>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH] Report that kernel is tainted if there were an OOPS before
Date: Mon, 16 Apr 2007 08:30:11 -0700 [thread overview]
Message-ID: <20070416083011.9ac0a9d7.randy.dunlap@oracle.com> (raw)
In-Reply-To: <46234E9E.6080107@sw.ru>
On Mon, 16 Apr 2007 14:23:26 +0400 Pavel Emelianov wrote:
> If the kernel OOPS-ed or BUG-ed then it probably should
> considered as tainted. Use die_counter introduced by many
> architectures to determine whether or not the kernel died.
>
> This saves a lot of time explaining oddities in the
> calltrace seen via SysRq-P.
argh, attachment...
+ * 'D' - An OOPS has hapened.
happened.
You also need to update Documentation/oops-tracing.txt.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-04-16 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 10:23 Pavel Emelianov
2007-04-16 15:30 ` Randy Dunlap [this message]
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=20070416083011.9ac0a9d7.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=devel@openvz.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xemul@sw.ru \
/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
all inboxes | Powered by JetHome®