Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls

From: Peter Zijlstra
Date: Wed Oct 19 2016 - 12:12:56 EST

On Wed, Oct 19, 2016 at 10:53:57AM +0900, Sergey Senozhatsky wrote:
> not to miss out a DEFERRED_WARN patch set...
> //hm, I can't find it online
> Subject: [RFC 0/5] printk: Implement WARN_*DEFERRED()
> Message-Id: <1474992135-14777-1-git-send-email-pmladek@xxxxxxxx>

That never hit lkml, that msgid does not resolve on marc and I can only
find a few replies in my local lkml archive.

Can't say I like the idea though. Its propagating the printk() failure
up into more APIs instead of actually fixing it.

Esp. for WARN and the like you do not want DEFERRED, because DEFERRED
means you'll likely never actually get to see the problem because we're
dead by the time 'later' happens.