mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shea Levy <shea@shealevy.com>
To: "Lluís Batlle i Rossell" <viric@viric.name>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hang opening a pipe written to by a child, with SIGCHLD
Date: Mon, 02 Apr 2012 10:49:10 -0400	[thread overview]
Message-ID: <4F79BC66.3010902@shealevy.com> (raw)
In-Reply-To: <20120402144611.GY3029@vicerveza.homeunix.net>

On 04/02/2012 10:46 AM, Lluís Batlle i Rossell wrote:
> Hello,
>
> I had troubles running a simple bash script where a child wrote to a named pipe
> before dying, and the parent opened and read the pipe.
>
> On a computer, my script hangs always. Also under 'strace'. Not under 'strace
> -f'. Thinking of some race, I wrote a small script that hangs in the linuxes I
> could try (3.2.11 now):
>
> ----------
> #!/var/run/current-system/sw/bin/bash
>
> PIPE=/tmp/pipe
>
> rm -f $PIPE
> mkfifo $PIPE
>
> function spawn {
>      echo DONE>  $PIPE
> }
>
> spawn sleep 1&
>
> while true; do
>      echo reading
>      while read LINE<  $PIPE; do
>          echo $LINE
>          spawn&
>      done
> done
> -------------
>
> bash uses SA_RESTART on SIGCHLD handler, and nevertheless the script halts at
> printing some amount of 'DONE'. Strace shows it's inside the open() call, while the open
> call has been interrupted by SIGCHLD. One of the computers I have hangs at the *first* DONE always, and that's why it's annoying to me.
>
> Can anyone reproduce this?

I've reproduced this on my system as well (3.3). No idea about cause though.

~Shea

  reply	other threads:[~2012-04-02 14:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 14:46 Lluís Batlle i Rossell
2012-04-02 14:49 ` Shea Levy [this message]
2012-04-02 18:50   ` Lluís Batlle i Rossell
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=4F79BC66.3010902@shealevy.com \
    --to=shea@shealevy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viric@viric.name \
    /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

Powered by JetHome