From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755637Ab2FUTir (ORCPT ); Thu, 21 Jun 2012 15:38:47 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:17858 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754189Ab2FUTip (ORCPT ); Thu, 21 Jun 2012 15:38:45 -0400 X-Authority-Analysis: v=2.0 cv=T6AOvo2Q c=1 sm=0 a=ZycB6UtQUfgMyuk2+PxD7w==:17 a=XQbtiDEiEegA:10 a=FlAZEPfbBygA:10 a=5SG0PmZfjMsA:10 a=Q9fys5e9bTEA:10 a=meVymXHHAAAA:8 a=ayC55rCoAAAA:8 a=zCIbDmUUZJ7B2bqkbYkA:9 a=PUjeQqilurYA:10 a=ZycB6UtQUfgMyuk2+PxD7w==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.67.80.29 Message-ID: <1340307523.27036.207.camel@gandalf.stny.rr.com> Subject: Re: [PATCH] printk: Add printk_flush() to force buffered text to console From: Steven Rostedt To: Joe Perches Cc: Greg Kroah-Hartman , Ingo Molnar , Fengguang Wu , LKML , Linus Torvalds , "kay.sievers" , "Paul E. McKenney" , Ingo Molnar , Andrew Morton Date: Thu, 21 Jun 2012 15:38:43 -0400 In-Reply-To: <1340304902.22218.12.camel@joe2Laptop> References: <20120614154153.GD17140@kroah.com> <1339693625.13377.242.camel@gandalf.stny.rr.com> <20120615042233.GA10973@localhost> <20120615043017.GA9587@kroah.com> <20120615120430.GB23681@gmail.com> <20120615231318.GD8205@kroah.com> <1339804415.25903.63.camel@gandalf.stny.rr.com> <20120618230337.GB23627@kroah.com> <1340069326.25903.177.camel@gandalf.stny.rr.com> <20120620122549.GA10561@gmail.com> <20120621171338.GF3270@kroah.com> <1340300509.27036.185.camel@gandalf.stny.rr.com> <1340302623.22065.9.camel@joe2Laptop> <1340303360.27036.194.camel@gandalf.stny.rr.com> <1340303969.22218.9.camel@joe2Laptop> <1340304566.27036.200.camel@gandalf.stny.rr.com> <1340304902.22218.12.camel@joe2Laptop> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.2.2-1+b1 Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2012-06-21 at 11:55 -0700, Joe Perches wrote: > > As it basically just acts like a barrier. "Make > > sure the output I printed actually gets out to the console before I > > continue". > > I think that'd be bad and hard to do. > > I think you mean simply attempt to deliver it > rather than guarantee it's actually emitted. > You mean due to contention on the printk console_sem? It should be delivered, but sure, if something else is already in the process of printing, and then the system crashes, the system is still acting the same as it did pre 3.5. -- Steve