[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=WodJER2g45u5pEw0edf+K4uYJjyt0w4ZfX9q=o1a7pYw@mail.gmail.com>
Date: Mon, 8 Apr 2013 15:45:31 -0700
From: Doug Anderson <dianders@...omium.org>
To: Stephen Warren <swarren@...dotorg.org>
Cc: Al Viro <viro@...iv.linux.org.uk>, Nathan Zimmer <nzimmer@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-fsdevel@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>,
David Woodhouse <dwmw2@...radead.org>, stable@...r.kernel.org,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>
Subject: Re: hangs on boot in 9984d7394618df9
Hi,
On Mon, Apr 8, 2013 at 3:17 PM, Stephen Warren <swarren@...dotorg.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists