panic: Allow warnings to set different taint flags

WARN() is used in some places to report firmware or hardware bugs that
are then worked-around.  These bugs do not affect the stability of the
kernel and should not set the flag for TAINT_WARN.  To allow for this,
add WARN_TAINT() and WARN_TAINT_ONCE() macros that take a taint number
as argument.

Architectures that implement warnings using trap instructions instead
of calls to warn_slowpath_*() now implement __WARN_TAINT(taint)
instead of __WARN().

Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Acked-by: Helge Deller <deller@gmx.de>
Tested-by: Paul Mundt <lethal@linux-sh.org>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/arch/sh/include/asm/bug.h b/arch/sh/include/asm/bug.h
index d02c01b3e6b9..6323f864d111 100644
--- a/arch/sh/include/asm/bug.h
+++ b/arch/sh/include/asm/bug.h
@@ -48,7 +48,7 @@ do {							\
                    "i" (sizeof(struct bug_entry)));     \
 } while (0)
 
-#define __WARN()                                        \
+#define __WARN_TAINT(taint)                             \
 do {                                                    \
         __asm__ __volatile__ (                          \
                 "1:\t.short %O0\n"                      \
@@ -57,7 +57,7 @@ do {							\
                  : "n" (TRAPA_BUG_OPCODE),              \
                    "i" (__FILE__),                      \
                    "i" (__LINE__),                      \
-                   "i" (BUGFLAG_WARNING),               \
+                   "i" (BUGFLAG_TAINT(taint)),          \
                    "i" (sizeof(struct bug_entry)));     \
 } while (0)