mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-19 06:17:08 +07:00
x86/entry, bug: Comment the instrumentation_begin() usage for WARN()
Explain the rationale for annotating WARN(), even though, strictly speaking printk() and friends are very much not safe in many of the places we put them. Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
This commit is contained in:
parent
6b643a07a7
commit
8e8bb06d19
@ -75,6 +75,12 @@ do { \
|
|||||||
unreachable(); \
|
unreachable(); \
|
||||||
} while (0)
|
} while (0)
|
||||||
|
|
||||||
|
/*
|
||||||
|
* This instrumentation_begin() is strictly speaking incorrect; but it
|
||||||
|
* suppresses the complaints from WARN()s in noinstr code. If such a WARN()
|
||||||
|
* were to trigger, we'd rather wreck the machine in an attempt to get the
|
||||||
|
* message out than not know about it.
|
||||||
|
*/
|
||||||
#define __WARN_FLAGS(flags) \
|
#define __WARN_FLAGS(flags) \
|
||||||
do { \
|
do { \
|
||||||
instrumentation_begin(); \
|
instrumentation_begin(); \
|
||||||
|
Loading…
Reference in New Issue
Block a user