Messages in this thread | | | Subject | Re: [PATCH 2/4] panic: Allow taint flag for warnings to be changed from TAINT_WARN | From | Andi Kleen <> | Date | Sun, 21 Mar 2010 20:10:43 +0100 |
| |
Ben Hutchings <ben@decadent.org.uk> writes:
> 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 usual TAINT_WARN flag. To allow for > this, add WARN_TAINT() and WARN_TAINT_ONCE() macros that take a taint > flag as argument. > > Architectures that implement warnings using trap instructions instead > of calls to warn_slowpath_*() must now implement __WARN_TAINT(taint) > instead of __WARN().
I guess this should enforce that at least some taint flag is set? (e.g. with a BUILD_BUG_ON)
-Andi
-- ak@linux.intel.com -- Speaking for myself only.
| |