Re: [RFC][PATCH 00/16] objtool: vmlinux.o and noinstr validation

Thomas Gleixner
2020-03-17T09:27:03Z

Masami Hiramatsu <mhiramat@kernel.org> writes:
> BTW, out of curiously, if BUG*() or WARN*() cases happens in the noinstr
> section, do we also need to move them (register dump, stack unwinding,
> printk, console output, etc.) all into noinstr section?

The current plan is to declare BUG()/WARN() "safe". On x86 it is kinda
safe as it uses UD2. That raises an exception which handles the bug/warn
after establishing the correct state.

Of course it's debatable, but moving all of this into the noinstr
section might be just a too wide scope.

Thanks,

tglx