From: Rusty Russell <rusty@rustcorp.com.au>
To: Dirk Morris <dmorris@metavize.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.2] Badness in futex_wait revisited
Date: Mon, 16 Feb 2004 22:42:44 +1100 [thread overview]
Message-ID: <20040216224244.3928d477.rusty@rustcorp.com.au> (raw)
In-Reply-To: <402D3DFF.4040609@metavize.com>
On Fri, 13 Feb 2004 13:13:35 -0800
Dirk Morris <dmorris@metavize.com> wrote:
> In reference to this previous post:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0401.1/1966.html
>
> I also get:
> Feb 13 11:43:52 timmy kernel: Call Trace:
> Feb 13 11:43:52 timmy kernel: [<c01387e1>] futex_wait+0x191/0x1a0
> Feb 13 11:43:52 timmy kernel: [<c011e9e0>] default_wake_function+0x0/0x20
> Feb 13 11:43:52 timmy kernel: [<c011e9e0>] default_wake_function+0x0/0x20
> Feb 13 11:43:52 timmy kernel: [<c0138abb>] do_futex+0x6b/0x80
> Feb 13 11:43:52 timmy kernel: [<c0138be6>] sys_futex+0x116/0x130
> Feb 13 11:43:52 timmy kernel: [<c010959f>] syscall_call+0x7/0xb
>
> I get this in 2.6.1 and 2.6.2.
> In userland a call to sem_wait returns with -1, and errno = -EINTR
Yes...
Please send your config. What's happening at the time?
(Andrew's patch was buggy, I fixed it and can send you an update).
Rusty.
--
there are those who do and those who hang on and you don't see too
many doers quoting their contemporaries. -- Larry McVoy
next prev parent reply other threads:[~2004-02-16 13:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 21:13 [2.6.2] Badness in futex_wait revisited Dirk Morris
2004-02-16 11:42 ` Rusty Russell [this message]
[not found] <40311703.8070309@metavize.com>
2004-02-17 4:39 ` 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
2004-04-01 1:57 ` 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=20040216224244.3928d477.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=dmorris@metavize.com \
--cc=linux-kernel@vger.kernel.org \
/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.