From: Robert Love <rml@tech9.net>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Hubertus Franke <frankeh@watson.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fast Userspace Mutexes III.
Date: 04 Mar 2002 20:50:06 -0500 [thread overview]
Message-ID: <1015293007.882.87.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44.0203041305250.1561-100000@blue1.dev.mcafeelabs.com>
In-Reply-To: <Pine.LNX.4.44.0203041305250.1561-100000@blue1.dev.mcafeelabs.com>
On Mon, 2002-03-04 at 17:15, Davide Libenzi wrote:
> That's great. What if the process holding the mutex dies while there're
> sleeping tasks waiting for it ?
I can't find an answer in the code (meaning the lock is lost...) and no
one has yet answered. Davide, have you noticed anything?
I think this needs a proper solution..
Robert Love
next prev parent reply other threads:[~2002-03-05 1:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 3:55 [PATCH] Fast Userspace Mutexes III Rusty Russell
2002-03-04 19:49 ` Robert Love
2002-03-04 20:13 ` Davide Libenzi
2002-03-04 20:20 ` Matthew Kirkwood
2002-03-04 20:48 ` Hubertus Franke
2002-03-04 22:15 ` Davide Libenzi
2002-03-05 1:50 ` Robert Love [this message]
2002-03-05 2:53 ` Davide Libenzi
2002-03-05 3:45 ` Rusty Russell
2002-03-05 3:55 ` Davide Libenzi
2002-03-05 6:11 ` Rusty Russell
2002-03-05 17:23 ` Davide Libenzi
2002-03-05 15:09 ` Hubertus Franke
2002-03-05 4:30 ` Edgar Toernig
2002-03-07 1:58 ` Richard Henderson
2002-03-07 2:10 ` Davide Libenzi
2002-03-05 4:48 ` Rusty Russell
2002-03-05 15:15 ` Hubertus Franke
2002-03-06 1:31 ` Rusty Russell
2002-03-05 1:34 ` Rusty Russell
2002-03-07 1:52 ` Richard Henderson
2002-03-07 3:39 ` Rusty Russell
2002-03-07 8:48 ` Richard Henderson
2002-03-07 9:17 ` 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=1015293007.882.87.camel@phantasy \
--to=rml@tech9.net \
--cc=davidel@xmailserver.org \
--cc=frankeh@watson.ibm.com \
--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 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.