Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757332Ab2F0LGR (ORCPT ); Wed, 27 Jun 2012 07:06:17 -0400 Received: from merlin.infradead.org ([205.233.59.134]:46412 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753168Ab2F0LGP convert rfc822-to-8bit (ORCPT ); Wed, 27 Jun 2012 07:06:15 -0400 Message-ID: <1340795162.10063.28.camel@twins> Subject: Re: cosmetic printk() issue with lockdep warning in arch/x86/kernel/alternative.c From: Peter Zijlstra To: Kay Sievers Cc: Ingo Molnar , Steven Rostedt , Andrew Morton , Linus Torvalds , Thomas Gleixner , linux-kernel@vger.kernel.org, Greg Kroah-Hartmann , Lennart Poettering Date: Wed, 27 Jun 2012 13:06:02 +0200 In-Reply-To: References: <20120627060939.GD14913@gmail.com> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 758 Lines: 17 On Wed, 2012-06-27 at 12:49 +0200, Kay Sievers wrote: > All we want is a reliable printk We too, but we define reliable differently. I want printk() to dump data ASAP so that it has better chance to get out of the system and onto my console in case of a crash. I don't give a rats arse about interleaved text, any text is better than no text. So if you go add separate buffers in there that will delay writing text, you're actively destroying printk(). Any change that makes it harder to get text out is bad. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/