From: Richard Weinberger <richard@nod.at>
To: "user-mode-linux-devel@lists.sourceforge.net"
<user-mode-linux-devel@lists.sourceforge.net>,
user-mode-linux-user@lists.sourceforge.net
Subject: [uml-devel] Advice to all glibc 2.12 users
Date: Sun, 09 Oct 2011 18:24:09 +0200 [thread overview]
Message-ID: <4E91CAA9.1070401@nod.at> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 336 bytes --]
glibc 2.12's pthread_cond_signal() is broken on UML because it does not
have FUTEX_WAKE_OP.
The issue got fixed in 2.12.2:
http://sourceware.org/ml/libc-alpha/2010-08/msg00019.html
Sadly, some distros (like CentOS 6.0) still ship glibc 2.12.1.
So you have to expect problems when them on top of UML...
Thanks,
//richard
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 377 bytes --]
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
[-- Attachment #3: Type: text/plain, Size: 194 bytes --]
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
reply other threads:[~2011-10-09 16:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E91CAA9.1070401@nod.at \
--to=richard@nod.at \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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