From: Russell King <rmk@arm.linux.org.uk>
To: akpm@linux-foundation.org
Cc: torvalds@linux-foundation.org, xemul@openvz.org,
linux-arch@vger.kernel.org, randy.dunlap@oracle.com
Subject: Re: [patch 041/234] Report that kernel is tainted if there was an OOPS
Date: Tue, 17 Jul 2007 19:10:03 +0100 [thread overview]
Message-ID: <20070717181003.GA16147@flint.arm.linux.org.uk> (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.
A bug causes an oops. Oops are counted. So, why do we need this
additional complexity when we already have the '#' counter in oops
dumps?
For instance, on ARM:
Unable to handle kernel NULL pointer dereference at virtual address 00000090
pgd = c0004000
[00000090] *pgd=00000000
Internal error: Oops: 817 [#1]
^^^^
This is the oops counter. Anything oops report from anyone other than the
first should always be questioned. Also note that this counter is not
re-settable at run time, unlike the taint flags.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-07-17 18:10 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
2007-07-17 18:10 ` Russell King [this message]
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=20070717181003.GA16147@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--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.