linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Nathan Zimmer <nzimmer@sgi.com>,
	akpm@linux-foundation.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 23:57:15 +0100	[thread overview]
Message-ID: <20130408225715.GX4068@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20130408224637.GW4068@ZenIV.linux.org.uk>

On Mon, Apr 08, 2013 at 11:46:37PM +0100, Al Viro wrote:

> Very interesting...  Just in case, could you try this on top of that
> branch and see if it triggers?
> 
> diff --git a/fs/pipe.c b/fs/pipe.c
> index 8ce279b..b6cd51b 100644
> --- a/fs/pipe.c
> +++ b/fs/pipe.c
> @@ -1022,6 +1022,11 @@ static int fifo_open(struct inode *inode, struct file *filp)
>  	/* We can only do regular read/write on fifos */
>  	filp->f_mode &= (FMODE_READ | FMODE_WRITE);
>  
> +	if (inode->i_sb->s_magic == PIPEFS_MAGIC) {
> +		WARN_ON(filp->f_flags & O_NONBLOCK);
> +		filp->f_flags &= ~O_NONBLOCK;
> +	}

*d'oh*

OK, I'm an idiot.  I see what's going on now...  Give me a few and I'll push
a fix.

  reply	other threads:[~2013-04-08 22:57 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
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 [this message]
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=20130408225715.GX4068@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --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 \
    /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).