From: Ingo Molnar <mingo@elte.hu>
To: Daniel Walker <dwalker@mvista.com>
Cc: tglx@linutronix.de, khilman@mvista.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] futex null pointer timeout
Date: Thu, 18 Jan 2007 08:38:16 +0100 [thread overview]
Message-ID: <20070118073816.GA28486@elte.hu> (raw)
In-Reply-To: <20070118002503.418478415@mvista.com>
* Daniel Walker <dwalker@mvista.com> wrote:
> This fix is mostly from Thomas ..
>
> The problem was that a futex can be called with a zero timeout (0
> seconds, 0 nanoseconds) and it's a valid expired timeout. However, the
> current futex in -rt assumes a zero timeout is an infinite timeout.
>
> Kevin Hilman found this using LTP's nptl01 test case which would soft
> hang occasionally.
>
> The patch reworks do_futex, and futex_wait* so a NULL pointer in the
> timeout position is infinite, and anything else is evaluated as a real
> timeout.
thanks, applied.
Ingo
next prev parent reply other threads:[~2007-01-18 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 0:25 [PATCH] futex null pointer timeout Daniel Walker
2007-01-18 6:51 ` Thomas Gleixner
2007-01-18 7:38 ` Ingo Molnar [this message]
2007-01-18 12:26 ` Pierre Peiffer
2007-01-18 12:44 ` Daniel Walker
2007-01-18 13:07 ` Ingo Molnar
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=20070118073816.GA28486@elte.hu \
--to=mingo@elte.hu \
--cc=dwalker@mvista.com \
--cc=khilman@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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