All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: David Singleton <dsingleton@mvista.com>
Cc: robustmutexes@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Robust Futex update
Date: Fri, 14 Oct 2005 07:35:16 +0200	[thread overview]
Message-ID: <20051014053516.GA21579@elte.hu> (raw)
In-Reply-To: <434DA382.1050100@mvista.com>


* David Singleton <dsingleton@mvista.com> wrote:

> Ingo,
>    here 's a patch for 2.6.14-rc4-rt1 that fixes two things:
> 
> 1) Deregister futex returns -EBUSY instead of -EINVAL if a thread 
> tries to deregister a pthread_mutex that another thread has locked.
> 
> 2) Make the fast path robust.  If a pthread_mutex is only locked in 
> user space we need to clear the owner when the thread dies.  This 
> makes both the 'rt_mutex is locked in the kernel' and the 
> 'pthread_mutex is only locked in user space' paths robust.

thanks, applied.

	Ingo

  reply	other threads:[~2005-10-14  5:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13  0:00 Robust Futex update David Singleton
2005-10-14  5:35 ` Ingo Molnar [this message]
2005-10-14  5:45 ` Ingo Molnar
2005-10-14 17:40   ` Khem Raj

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=20051014053516.GA21579@elte.hu \
    --to=mingo@elte.hu \
    --cc=dsingleton@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robustmutexes@lists.osdl.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.