From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Rob Landley <rob@landley.net>,
Michael Ellerman <mpe@ellerman.id.au>,
Yury Norov <ynorov@caviumnetworks.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Prarit Bhargava <prarit@redhat.com>,
Yang Shi <yang.shi@linaro.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Kees Cook <keescook@chromium.org>,
Emese Revfy <re.emese@gmail.com>,
Fabian Frederick <fabf@skynet.be>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: Patch 0727d35de ("Make initramfs honor CONFIG_DEVTMPFS_MOUNT") breaks boot
Date: Tue, 12 Sep 2017 09:42:43 +0900 [thread overview]
Message-ID: <20170912004243.GA3963@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20170911114535.GL8741@pathway.suse.cz>
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
next prev parent reply other threads:[~2017-09-12 0:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 12:05 Yury Norov
2017-05-23 2:07 ` Rob Landley
2017-05-23 8:01 ` Yury Norov
2017-05-23 17:40 ` Rob Landley
2017-05-23 21:32 ` Yury Norov
2017-05-23 23:08 ` Yury Norov
2017-05-25 5:55 ` Rob Landley
2017-05-25 6:13 ` Michael Ellerman
2017-09-10 23:43 ` Rob Landley
2017-09-11 11:45 ` Petr Mladek
2017-09-12 0:42 ` Sergey Senozhatsky [this message]
2017-09-13 2:45 ` Rob Landley
[not found] ` <CAP2kuOwkM7hr5nOtrRSRdXcPi2y3KHVf4yFdDN1JW1o_mWo0yw@mail.gmail.com>
2017-05-25 13:44 ` Leo Yan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170912004243.GA3963@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=fabf@skynet.be \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mpe@ellerman.id.au \
--cc=pmladek@suse.com \
--cc=prarit@redhat.com \
--cc=re.emese@gmail.com \
--cc=rob@landley.net \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=yang.shi@linaro.org \
--cc=ynorov@caviumnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®