On (09/28/17 14:07), Peter Zijlstra wrote:
[..]
> > Nah.. WARN's _should_ not trigger. If they do we fix that.
> >
> > Getting a lockdep splat after a WARN is something I can live with.
> >
> > And you really don't want that deferred nonsense for WARNs, because that
> > means you'll risk not over getting the output.
>
> Note that I'm not likely to care too much either way, because I'm simply
> not using any of that printk() nonsense ;-)
>
>
> I'll repost my patches now; otherwise I'll forget again anyway.
#define printk printk_deferred
should also do the trick and... make the kernel great again! :)
-ss
