From: "Josef 'Jeff' Sipek" <jeffpc@josefsipek.net>
To: Nur Hussein <nurhussein@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
akpm@linux-foundation.org, a.p.zijlstra@chello.nl,
gregkh@suse.de
Subject: Re: [PATCH 1/1] Taint kernel after WARN_ON(condition)
Date: Mon, 11 Feb 2008 15:20:07 -0500 [thread overview]
Message-ID: <20080211202007.GC25262@josefsipek.net> (raw)
In-Reply-To: <20080211195222.GA5809@gandalf.middleearth>
On Tue, Feb 12, 2008 at 03:52:22AM +0800, Nur Hussein wrote:
> This patch will taint the kernel with a new flag, 'W', whenever a
> warning is issued with WARN_ON(condition). Whenever a warning occurs, it
> is helpful to record this within the kernel state as a taint. When a BUG
> happens, it'd be useful to know if it was also preceded by a WARN.
Any architecture that has it's own WARN_ON will not taint the kernel.
Speaking of WARN_ON...
$ git-grep "[^A-Za-z_0-9]WARN_ON(1)" | wc -l
180
Maybe making a WARN() (similar to BUG) that does an unconditional warning
(and sets the taint flag) and having a simple wrapper around it for the
conditional WARN_ON would be worth it? Hm...looks like some of the USB folks
have a #define'd WARN to something quite a bit more complex (format string,
etc.)
Josef 'Jeff' Sipek.
--
Linux, n.:
Generous programmers from around the world all join forces to help
you shoot yourself in the foot for free.
next prev parent reply other threads:[~2008-02-11 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 19:52 Nur Hussein
2008-02-11 20:20 ` Josef 'Jeff' Sipek [this message]
2008-02-11 20:28 ` Randy Dunlap
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=20080211202007.GC25262@josefsipek.net \
--to=jeffpc@josefsipek.net \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nurhussein@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome