public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Lukasz Majewski <lukma@denx.de>,
	Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] misc: Fix tst-select timeout handling (BZ#27648)
Date: Fri, 26 Mar 2021 14:15:15 -0300	[thread overview]
Message-ID: <a389a1a5-a6b1-1735-61c9-25417fe24c81@linaro.org> (raw)
In-Reply-To: <20210326104346.05155e6b@jawa>



On 26/03/2021 06:43, Lukasz Majewski wrote:
> Hi Adhemerval,
> 
>> Instead of polling the stderr, create two pipes and fork to check
>> if child timeout as expected similar to tst-pselect.c.  Also lower
>> the timeout value.
> 
> I'm just wondering why this approach (with pipes) is more safe than
> polling stderr?

Using the standard file descriptor is tricky because they can be
either closed or redirected by the parent. 

 

      reply	other threads:[~2021-03-26 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 20:00 Adhemerval Zanella
2021-03-25 21:06 ` H.J. Lu
2021-03-26  9:43 ` Lukasz Majewski
2021-03-26 17:15   ` Adhemerval Zanella [this message]

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=a389a1a5-a6b1-1735-61c9-25417fe24c81@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=lukma@denx.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).