From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751119AbdILAmt (ORCPT ); Mon, 11 Sep 2017 20:42:49 -0400 Received: from mail-pg0-f52.google.com ([74.125.83.52]:38473 "EHLO mail-pg0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750999AbdILAmr (ORCPT ); Mon, 11 Sep 2017 20:42:47 -0400 X-Google-Smtp-Source: ADKCNb7+I8Yq8sc2A8eyMJRgn6Q0n9t2Sy1nd1Fvwub9EsYrZz22fjgRrDajPx+vjBmK8opILrTVtg== Date: Tue, 12 Sep 2017 09:42:43 +0900 From: Sergey Senozhatsky To: Petr Mladek Cc: Rob Landley , Michael Ellerman , Yury Norov , Andrew Morton , "linux-kernel@vger.kernel.org" , Prarit Bhargava , Yang Shi , Rasmus Villemoes , Kees Cook , Emese Revfy , Fabian Frederick , Linus Torvalds , Sergey Senozhatsky Subject: Re: Patch 0727d35de ("Make initramfs honor CONFIG_DEVTMPFS_MOUNT") breaks boot Message-ID: <20170912004243.GA3963@jagdpanzerIV.localdomain> References: <20170522120550.ekrq6ipfmkdtlxjo@yury-N73SV> <7d91fb6b-9a21-ceb6-6c08-4bc14a15ada2@landley.net> <20170523080159.2yetdh4qqt2pmha6@yury-N73SV> <66dd96ec-b170-0bf6-7746-5466270b3e15@landley.net> <87fufta2gi.fsf@concordia.ellerman.id.au> <1fb53a8c-6c17-1de2-493c-0bff403c9ff9@landley.net> <20170911114535.GL8741@pathway.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170911114535.GL8741@pathway.suse.cz> User-Agent: Mutt/1.9.0 (2017-09-02) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (09/11/17 13:45), Petr Mladek wrote: [..] > > Except for the second printk line: If you boot with rdinit=/bin/hush > > then the first time you mount -t devtmpfs /dev /dev after boot (with > > CONFIG_DEVTMPFS_MOUNT already having mounted it), you get the 0 return > > value but the last printk() doesn't output? The second and later times > > you repeat it, both printk() lines are output. > > > > What's up with printk? > > > > (I added the second printk because the _first_ one wasn't outputting > > that first time. Something is happening to flush the printk() queue > > instead of writing it out? > Maybe, we could setup the timer via an irq_work. We already use > this trick for flushing deferred printk and waking klogd. > It is not nice but it would be easier than the previous mess. printk() and printf() have similar behaviour here. both flush on \n. so let's keep it the way it is? -ss