From: Andrew Morton <akpm@osdl.org>
To: rusty@rustcorp.com.au, dmorris@metavize.com, jamie@shareable.org,
linux-kernel@vger.kernel.org
Subject: Re: [2.6.2] Badness in futex_wait revisited
Date: Thu, 1 Apr 2004 01:24:52 -0800 [thread overview]
Message-ID: <20040401012452.2c467108.akpm@osdl.org> (raw)
In-Reply-To: <20040401003418.6485d6bf.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
>
> > > Here ya go. :)
>
> Dirk, thanks for that. It's worth its weight.
>
> >
> > Doesn't work for me (2.6.5-rc1 Debian unstable 2xi686).
>
> It works here.
Then again, I only saw the debug messages on the wakeup path. I'm unable
to trigger the warning in futex_wait().
next prev parent reply other threads:[~2004-04-01 9:25 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
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 [this message]
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=20040401012452.2c467108.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dmorris@metavize.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox