linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	Nathan Zimmer <nzimmer@sgi.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	David Woodhouse <dwmw2@infradead.org>,
	stable@vger.kernel.org,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: hangs on boot in 9984d7394618df9
Date: Mon, 8 Apr 2013 15:45:31 -0700	[thread overview]
Message-ID: <CAD=FV=WodJER2g45u5pEw0edf+K4uYJjyt0w4ZfX9q=o1a7pYw@mail.gmail.com> (raw)
In-Reply-To: <516341ED.5060803@wwwdotorg.org>

Hi,

On Mon, Apr 8, 2013 at 3:17 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> Anyway, I've just pushed a splitup of that commit (carved in 3 pieces)
>> into vfs.git#pipe-splitup; could you check which part triggers that
>> hang?  Should propagate in a few...
>
> It looks like "pipe: unify ->release() and ->open()" introduces the
> problem. Note that I had to add a prototype for fifo_open() before the
> structs that reference it for that commit to compile.

It sounds like Stephen has provided you the info you needed so not
doing any extra testing now, but I figured I'd chime in that I hit
problems this morning with linux-next and it appears to be the same
thing.  I did a revert of 9984d7394618df9 and (plus a revert of a
handful of patches to the same file) and problems are resolved.  The
failure case is really weird in that everything works well booting to
a simple /bin/bash but fails when you do more complex tasks.

Anyway: If you need some extra testing feel free to CC me.

-Doug

  reply	other threads:[~2013-04-08 22:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <515DB465.1060004@sgi.com>
     [not found] ` <20130404204459.GU21522@ZenIV.linux.org.uk>
     [not found]   ` <515F0456.9040803@sgi.com>
     [not found]     ` <20130405173623.GE4068@ZenIV.linux.org.uk>
     [not found]       ` <515F3A71.9080008@sgi.com>
     [not found]         ` <20130405210042.GH4068@ZenIV.linux.org.uk>
     [not found]           ` <5162E36F.5020305@sgi.com>
     [not found]             ` <20130408155847.GS4068@ZenIV.linux.org.uk>
     [not found]               ` <51632DF8.2080402@sgi.com>
     [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 [this message]
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
2013-04-08 22:46                       ` Al Viro
2013-04-08 22:57                         ` Al Viro
2013-04-10 10:44 Sedat Dilek

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='CAD=FV=WodJER2g45u5pEw0edf+K4uYJjyt0w4ZfX9q=o1a7pYw@mail.gmail.com' \
    --to=dianders@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nzimmer@sgi.com \
    --cc=stable@vger.kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).