Commit a7bed27a authored by Kees Cook's avatar Kees Cook Committed by Linus Torvalds
Browse files

bug: fix "cut here" location for __WARN_TAINT architectures

Prior to v4.11, x86 used warn_slowpath_fmt() for handling WARN()s.
After WARN() was moved to using UD0 on x86, the warning text started
appearing _before_ the "cut here" line.  This appears to have been a
long-standing bug on architectures that used __WARN_TAINT, but it didn't
get fixed.

v4.11 and earlier on x86:

  ------------[ cut here ]------------
  WARNING: CPU: 0 PID: 2956 at drivers/misc/lkdtm_bugs.c:65 lkdtm_WARNING+0x21/0x30
  This is a warning message
  Modules linked in:

v4.12 and later on x86:

  This is a warning message
  ------------[ cut here ]------------
  WARNING: CPU: 1 PID: 2982 at drivers/misc/lkdtm_bugs.c:68 lkdtm_WARNING+0x15/0x20
  Modules linked in:

With this fix:

  ------------[ cut here ]------------
  This is a warning message
  WARNING: CPU: 3 PID: 3009 at drivers/misc/lkdtm_bugs.c:67 lkdtm_WARNING+0x15/0x20

Since the __FILE__ reporting happens as part of the UD0 handler, it
isn't trivial to move the message to after the WARNING line, but at
least we can fix the position of the "cut here" line so all the various
logging tools will start including the actual runtime warning message
again, when they follow the instruction and "cut here".

Fixes: 9a93848f

 ("x86/debug: Implement __WARN() using UD0")
Signed-off-by: default avatarKees Cook <>
Cc: Peter Zijlstra (Intel) <>
Cc: Josh Poimboeuf <>
Cc: Fengguang Wu <>
Cc: Arnd Bergmann <>
Cc: Ingo Molnar <>
Signed-off-by: default avatarAndrew Morton <>
Signed-off-by: default avatarLinus Torvalds <>
parent 2a8358d8
......@@ -92,10 +92,11 @@ extern void warn_slowpath_null(const char *file, const int line);
#define __WARN_printf_taint(taint, arg...) \
warn_slowpath_fmt_taint(__FILE__, __LINE__, taint, arg)
extern __printf(1, 2) void __warn_printk(const char *fmt, ...);
#define __WARN_printf(arg...) do { printk(arg); __WARN(); } while (0)
#define __WARN_printf(arg...) do { __warn_printk(arg); __WARN(); } while (0)
#define __WARN_printf_taint(taint, arg...) \
do { printk(arg); __WARN_TAINT(taint); } while (0)
do { __warn_printk(arg); __WARN_TAINT(taint); } while (0)
/* used internally by panic.c */
......@@ -520,7 +520,8 @@ void __warn(const char *file, int line, void *caller, unsigned taint,
if (args)
if (file)
pr_warn("WARNING: CPU: %d PID: %d at %s:%d %pS\n",
......@@ -584,9 +585,22 @@ EXPORT_SYMBOL(warn_slowpath_fmt_taint);
void warn_slowpath_null(const char *file, int line)
__warn(file, line, __builtin_return_address(0), TAINT_WARN, NULL, NULL);
void __warn_printk(const char *fmt, ...)
va_list args;
va_start(args, fmt);
vprintk(fmt, args);
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment