linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lluís Batlle i Rossell" <viric@viric.name>
To: Shea Levy <shea@shealevy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hang opening a pipe written to by a child, with SIGCHLD
Date: Mon, 2 Apr 2012 20:50:57 +0200	[thread overview]
Message-ID: <20120402185057.GB3029@vicerveza.homeunix.net> (raw)
In-Reply-To: <4F79BC66.3010902@shealevy.com>

On Mon, Apr 02, 2012 at 10:49:10AM -0400, Shea Levy wrote:
> On 04/02/2012 10:46 AM, Lluís Batlle i Rossell wrote:
> >Can anyone reproduce this?
> 
> I've reproduced this on my system as well (3.3). No idea about cause though.
> 

Thank you Shea,

with a little change, adding "sleep 0.1" makes it hang early in all (few)
linuces I tried: Let me know if this helps you reproduce the problem.

As before, hangs under strace, does not hang under 'strace -f'. Sorry if I'm
misunderstanding something.

New script:
----------
#!/bin/sh
                                                                                                                   
PIPE=/tmp/pipe
                                                                                                                   
rm -f $PIPE
mkfifo $PIPE
set -x
                                                                                                                   
spawn() {
    sleep 0.1
    echo DONE > $PIPE
}

spawn &

while true; do
    while read LINE < $PIPE; do
        echo $LINE
        spawn &
    done
done
-----------

Regards,
Lluís.

  reply	other threads:[~2012-04-02 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 14:46 Hang opening a pipe written to by a child, with SIGCHLD Lluís Batlle i Rossell
2012-04-02 14:49 ` Shea Levy
2012-04-02 18:50   ` Lluís Batlle i Rossell [this message]
2012-04-02 20:20     ` Lluís Batlle i Rossell
     [not found] <20120409120326.f0ce7a94.akpm@linux-foundation.org>
2012-04-10 22:55 ` Oleg Nesterov
2012-04-10 23:12   ` Oleg Nesterov

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=20120402185057.GB3029@vicerveza.homeunix.net \
    --to=viric@viric.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shea@shealevy.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;
as well as URLs for NNTP newsgroup(s).