From: Nathan Zimmer <email@example.com>
To: Doug Anderson <firstname.lastname@example.org>
Cc: Al Viro <email@example.com>,
Stephen Warren <firstname.lastname@example.org>,
Andrew Morton <email@example.com>,
"Eric W. Biederman" <firstname.lastname@example.org>,
David Woodhouse <email@example.com>,
Subject: Re: hangs on boot in 9984d7394618df9
Date: Tue, 9 Apr 2013 12:12:34 -0500 [thread overview]
Message-ID: <51644C02.firstname.lastname@example.org> (raw)
On 04/08/2013 06:46 PM, Doug Anderson wrote:
> On Mon, Apr 8, 2013 at 4:06 PM, Al Viro <email@example.com> wrote:
>> Folks, see if vfs.git#experimental works for you; the PITA had apparently
>> been caused by change of open() semantics for /proc/<pid>/fd/<some_pipe> -
>> it started to behave like a FIFO, i.e. wait for peer to show up. Normally
>> that's not a problem, but if you have closed e.g. the write end of a pipe
>> and try to open /proc/<pid>/fd/<read_end_of_pipe>, you'll get open() waiting
>> for writers to appear. Which isn't what we used to do here (open succeeded
>> immediately) and apparently that was enough to trip drakut.
>> Branch head should be at 574179469f7370aadb9cbac1ceca7c3723c17bee.
> That branch booted fine for me and didn't show any problems.
> I wasn't easily able to merge onto linux-next and test there though.
> I tried applying these the 4 top commits of your branch to
> "next-20130408" and it didn't solve my problems. A full merge of your
> branch to linux-next showed conflicts and I didn't dig.
I booted great for me too.
Also the numbers from the scaling test are improved also, at least on my
I'll verify on a 512 or larger box when I have the chance.
However I think I still should to provide some relief for the older kernels.
next prev parent reply other threads:[~2013-04-09 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <515DB465.firstname.lastname@example.org>
[not found] ` <20130404204459.GU21522@ZenIV.linux.org.uk>
[not found] ` <515F0456.email@example.com>
[not found] ` <20130405173623.GE4068@ZenIV.linux.org.uk>
[not found] ` <515F3A71.firstname.lastname@example.org>
[not found] ` <20130405210042.GH4068@ZenIV.linux.org.uk>
[not found] ` <5162E36F.email@example.com>
[not found] ` <20130408155847.GS4068@ZenIV.linux.org.uk>
[not found] ` <51632DF8.firstname.lastname@example.org>
[not found] ` <20130408212327.GU4068@ZenIV.linux.org.uk>
[not found] ` <20130408214834.GV4068@ZenIV.linux.org.uk>
2013-04-08 22:17 ` hangs on boot in 9984d7394618df9 Stephen Warren
2013-04-08 22:45 ` Doug Anderson
2013-04-08 23:06 ` Al Viro
2013-04-08 23:20 ` Stephen Warren
2013-04-08 23:46 ` Doug Anderson
2013-04-09 17:12 ` Nathan Zimmer [this message]
2013-04-08 22:46 ` Al Viro
2013-04-08 22:57 ` Al Viro
2013-04-10 10:44 Sedat Dilek
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).