All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Morris <dmorris@metavize.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.2] Badness in futex_wait revisited
Date: Wed, 31 Mar 2004 09:38:33 -0800	[thread overview]
Message-ID: <406B0219.3000309@metavize.com> (raw)
In-Reply-To: <20040331165656.GG19280@mail.shareable.org>

No, I still get them in 2.6.4

To my knowledge, they only happen when one thread is blocked in a system 
call
and another thread makes a system("foo bar") call.
The blocked thread will return with EINTR.
I see this usually in sem_wait, but also in epoll_wait sometimes.

Is it possible system() is causing the wrong process to get woken up?

Let me know if you need any further information, I can reproduce it 
consistently.

Jamie Lokier wrote:

>Was the badness in futex_wait problem ever resolved?
>
>-- Jamie
>  
>


  reply	other threads:[~2004-03-31 17:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <40311703.8070309@metavize.com>
2004-02-17  4:39 ` [2.6.2] Badness in futex_wait revisited Rusty Russell
2004-02-17  5:27   ` Andrew Morton
2004-02-18  4:14     ` Rusty Russell
2004-02-17 19:55   ` Dirk Morris
2004-03-31 16:56   ` Jamie Lokier
2004-03-31 17:38     ` Dirk Morris [this message]
2004-03-31 18:32       ` Jamie Lokier
2004-03-31 18:59         ` Dirk Morris
2004-04-01  2:16           ` Rusty Russell
2004-04-01  8:34             ` Andrew Morton
2004-04-01  9:24               ` Andrew Morton
2004-04-01  1:57     ` Rusty Russell
2004-02-13 21:13 Dirk Morris
2004-02-16 11:42 ` Rusty Russell

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=406B0219.3000309@metavize.com \
    --to=dmorris@metavize.com \
    --cc=akpm@osdl.org \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.