From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S946039AbcJSQMx (ORCPT ); Wed, 19 Oct 2016 12:12:53 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:60418 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S938793AbcJSOUk (ORCPT ); Wed, 19 Oct 2016 10:20:40 -0400 Date: Wed, 19 Oct 2016 11:30:51 +0200 From: Peter Zijlstra To: Sergey Senozhatsky Cc: Sergey Senozhatsky , Petr Mladek , Andrew Morton , Jan Kara , Tejun Heo , Calvin Owens , Thomas Gleixner , Mel Gorman , Steven Rostedt , Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls Message-ID: <20161019093051.GG3102@twins.programming.kicks-ass.net> References: <20161018154045.7364-1-sergey.senozhatsky@gmail.com> <20161018170754.GA3102@twins.programming.kicks-ass.net> <20161019015357.GC513@swordfish> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161019015357.GC513@swordfish> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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@suse.com> 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.