linux-kernel - Re: [PATCH] Report that kernel is tainted if there were an OOPS before

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20070416083011.9ac0a9d7.randy.dunlap@oracle.com>
Date:	Mon, 16 Apr 2007 08:30:11 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Pavel Emelianov <xemul@...ru>
Cc:	Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-arch@...r.kernel.org, devel@...nvz.org
Subject: Re: [PATCH] Report that kernel is tainted if there were an OOPS
 before

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 ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/