From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750883AbdBBCLV (ORCPT ); Wed, 1 Feb 2017 21:11:21 -0500 Received: from mail-pg0-f68.google.com ([74.125.83.68]:35213 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750774AbdBBCLT (ORCPT ); Wed, 1 Feb 2017 21:11:19 -0500 Date: Thu, 2 Feb 2017 11:11:34 +0900 From: Sergey Senozhatsky To: Petr Mladek Cc: Peter Zijlstra , Jan Kara , Ross Zwisler , Sergey Senozhatsky , Ross Zwisler , Andrew Morton , Linus Torvalds , Tejun Heo , Calvin Owens , Steven Rostedt , Ingo Molnar , Andy Lutomirski , Peter Hurley , LKML , Sergey Senozhatsky Subject: Re: [PATCHv7 6/8] printk: use printk_safe buffers in printk Message-ID: <20170202021134.GC1954@jagdpanzerIV.localdomain> References: <20161227141611.940-1-sergey.senozhatsky@gmail.com> <20161227141611.940-7-sergey.senozhatsky@gmail.com> <20170201090625.GC11567@quack2.suse.cz> <20170201093739.GT6515@twins.programming.kicks-ass.net> <20170201153910.GL6620@pathway.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170201153910.GL6620@pathway.suse.cz> User-Agent: Mutt/1.7.2 (2016-11-26) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (02/01/17 16:39), Petr Mladek wrote: [..] > I guess that you are talking about the introduction of > #define SCHED_WARN_ON(x) WARN_ONCE(x, #x) my guess would be that Jan was talking about printk_deferred() patch. it's on my TODO list. I want to entirely remove console_sem and scheduler out of printk() path. that's the only way to make printk() deadlock safe. -ss