From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
linuxppc-dev@lists.linuxppc.org
Subject: problems with linuxthreads under your latest glibc 15C rpms
Date: Thu, 27 Jul 2000 21:05:09 -0400 [thread overview]
Message-ID: <3980DC45.554DB39D@ivey.uwo.ca> (raw)
Hi Franz,
Whoops I forgot to attach the patch to fix this (against your latest
glibc-2.1.3-15c src rpm).
--- linuxthreads/mutex.c.prev Thu Jul 27 20:57:28 2000
+++ linuxthreads/mutex.c Thu Jul 27 20:59:06 2000
@@ -50,7 +50,9 @@
switch(mutex->__m_kind) {
case PTHREAD_MUTEX_FAST_NP:
retcode = __pthread_trylock(&mutex->__m_lock);
- mutex->__m_owner = thread_self();
+ if (retcode == 0) {
+ mutex->__m_owner = thread_self();
+ }
return retcode;
case PTHREAD_MUTEX_RECURSIVE_NP:
self = thread_self();
I will let you know if I find any more funny things.
Thanks,
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-28 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-28 1:05 Kevin B. Hendricks [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-28 0:57 problems with linuxthreads under your latest glibc 15C rpms Kevin B. Hendricks
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=3980DC45.554DB39D@ivey.uwo.ca \
--to=khendricks@ivey.uwo.ca \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).