Clean up cut-here even harder (was Re: [PATCH 1/3] powerpc: don't use __WARN() for WARN_ON())

2019-08-19 Thread Kees Cook
On Mon, Aug 19, 2019 at 09:28:03AM -0700, Kees Cook wrote: > On Mon, Aug 19, 2019 at 01:06:28PM +, Christophe Leroy wrote: > > __WARN() used to just call __WARN_TAINT(TAINT_WARN) > > > > But a call to printk() has been added in the commit identified below > > to print a " cut here " li

Re: [PATCH 1/3] powerpc: don't use __WARN() for WARN_ON()

2019-08-19 Thread Kees Cook
On Mon, Aug 19, 2019 at 01:06:28PM +, Christophe Leroy wrote: > __WARN() used to just call __WARN_TAINT(TAINT_WARN) > > But a call to printk() has been added in the commit identified below > to print a " cut here " line. > > This change only applies to warnings using __WARN(), which m

[PATCH 1/3] powerpc: don't use __WARN() for WARN_ON()

2019-08-19 Thread Christophe Leroy
__WARN() used to just call __WARN_TAINT(TAINT_WARN) But a call to printk() has been added in the commit identified below to print a " cut here " line. This change only applies to warnings using __WARN(), which means WARN_ON() where the condition is constant at compile time. For WARN_ON()