From: David Singleton <daviado@gmail.com>
To: tglx@linutronix.de, mingo@elte.hu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Robust mutexes (-rt)
Date: Thu, 2 Feb 2006 19:18:59 -0800 [thread overview]
Message-ID: <b324b5ad0602021918s45a94b8es5f35618918aa4a7a@mail.gmail.com> (raw)
In-Reply-To: <1138909303.29087.51.camel@localhost.localdomain>
Thomas,
here is a patch that fixes the -EINTR problem and a fix for Dinakar's
simple futex deadlock test program. When Esben's new deadlock detection
is ready I plan to use it for robust futex deadlock detection, both simple and
circular deadlock detection.
http://source.mvista.com:~dsingleton/patch-2.6.15-rt16-rf1
include/linux/futex.h | 3 +++
kernel/futex.c | 3 +++
kernel/rt.c | 19 ++++++++++++++++++-
3 files changed, 24 insertions(+), 1 deletion(-)
David
> Just another problem:
>
> pthread_mutex_lock() of a robust mutex returns -EINTR, which is wrong by
> the specification. We encountered this in an application. Not sure what
> to do about that. It needs either a fix in glibc or the kernel could
> handle it via a restart function. That happens when a signal is
> delivered to the thread while the thread is blocked on the mutex.
>
> tglx
>
>
>
>
>
next parent reply other threads:[~2006-02-03 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1138740179.5184.34.camel@localhost.localdomain>
[not found] ` <b324b5ad0602011528g7ef81dc1ua0ecad2d73348d89@mail.gmail.com>
[not found] ` <1138863989.29087.24.camel@localhost.localdomain>
[not found] ` <1138909303.29087.51.camel@localhost.localdomain>
2006-02-03 3:18 ` David Singleton [this message]
2006-02-03 6:04 ` Thomas Gleixner
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=b324b5ad0602021918s45a94b8es5f35618918aa4a7a@mail.gmail.com \
--to=daviado@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®