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, 3 insertions, 3 deletions

diff --git a/arch/powerpc/include/asm/bug.h b/arch/powerpc/include/asm/bug.h
index 2c15212e1700..065c590c991d 100644
--- a/arch/powerpc/include/asm/bug.h
+++ b/arch/powerpc/include/asm/bug.h
@@ -85,12 +85,12 @@
         }                                                       \
 } while (0)
 
-#define __WARN() do {                                           \
+#define __WARN_TAINT(taint) do {                                \
         __asm__ __volatile__(                                   \
                 "1:     twi 31,0,0\n"                           \
                 _EMIT_BUG_ENTRY                                 \
                 : : "i" (__FILE__), "i" (__LINE__),             \
-                  "i" (BUGFLAG_WARNING),                        \
+                  "i" (BUGFLAG_TAINT(taint)),                   \
                   "i" (sizeof(struct bug_entry)));              \
 } while (0)
 
@@ -104,7 +104,7 @@
                 "1:     "PPC_TLNEI"     %4,0\n"                 \
                 _EMIT_BUG_ENTRY                                 \
                 : : "i" (__FILE__), "i" (__LINE__),             \
-                  "i" (BUGFLAG_WARNING),                        \
+                  "i" (BUGFLAG_TAINT(TAINT_WARN)),              \
                   "i" (sizeof(struct bug_entry)),               \
                   "r" (__ret_warn_on));                         \
         }                                                       \