public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kiszka at siemens dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/11588] pthread condvars are not priority inheritance aware
Date: Mon, 14 Feb 2011 17:28:00 -0000	[thread overview]
Message-ID: <bug-11588-131-ZuVpXowMkk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11588-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=11588

Jan Kiszka <jan.kiszka at siemens dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jan.kiszka at siemens dot
                   |                            |com

--- Comment #17 from Jan Kiszka <jan.kiszka at siemens dot com> 2011-02-14 17:28:26 UTC ---
(In reply to comment #16)
> Is there any chance that this issue is going to make any progress ? It affects
> real users and we have a working solution for it.

I can only confirm this. We just saw that unfortunate deadlock again in real
application (something to be shipped in products). We ran into it before, but
this time we finally realized that it's not due to an outdated glibc but rather
a still unfixed bug.

Our applications consist of dozens of real-time threads at different prio
levels and practically can't be reworked to avoid cond variables in RT threads.
So we really need a solution, and that preferably without having to carry our
own patched glibc versions.

Thanks,
Jan

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


       reply	other threads:[~2011-02-14 17:28 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11588-131@http.sourceware.org/bugzilla/>
2011-02-14 17:28 ` jan.kiszka at siemens dot com [this message]
2012-06-05 16:31 ` dvhart at linux dot intel.com
2012-06-05 16:37 ` jan.kiszka at siemens dot com
2012-10-25 11:03 ` triegel at redhat dot com
2012-12-19 10:51 ` schwab@linux-m68k.org
2013-01-19 16:13 ` scot4spam at yahoo dot com
2013-04-05 17:54 ` davidh at realtimeint dot com
2013-04-06  9:15 ` stano at meduna dot org
2013-10-17 21:16 ` gratian.crisan at ni dot com
2013-10-17 21:18 ` gratian.crisan at ni dot com
2013-10-17 21:22 ` gratian.crisan at ni dot com
2013-10-17 21:24 ` gratian.crisan at ni dot com
2013-11-15 17:36 ` gratian.crisan at ni dot com
2014-02-08  0:47 ` davidh at realtimeint dot com
2014-02-08  0:58 ` allan at archlinux dot org
2014-02-08  1:06 ` joseph at codesourcery dot com
2014-02-08  1:20 ` triegel at redhat dot com
2014-02-08  3:52 ` gratian.crisan at ni dot com
2014-02-10 23:00 ` darren.hart at intel dot com
2014-02-11  2:32 ` triegel at redhat dot com
2014-02-16 16:56 ` jackie.rosen at hushmail dot com
2014-02-20 17:44 ` john.ogness at linutronix dot de
2014-02-20 18:41 ` darren.hart at intel dot com
2014-02-20 18:42 ` darren.hart at intel dot com
2014-02-20 19:22 ` gratian.crisan at ni dot com
2014-02-21  8:44 ` john.ogness at linutronix dot de
2014-02-26 17:11 ` gratian.crisan at ni dot com
2014-03-31 19:31 ` darren.hart at intel dot com
2014-04-17 14:53 ` gratian.crisan at ni dot com
2014-04-17 15:15 ` darren.hart at intel dot com
2014-04-30 19:53 ` gratian.crisan at ni dot com
2014-05-28 19:42 ` schwab at sourceware dot org
2014-06-30 18:06 ` fweimer at redhat dot com
2014-07-07 20:39 ` gratian.crisan at ni dot com
2014-07-07 20:40 ` gratian.crisan at ni dot com
2014-07-07 20:41 ` gratian.crisan at ni dot com
2014-07-07 20:43 ` gratian.crisan at ni dot com
2014-07-07 20:44 ` gratian.crisan at ni dot com
2014-07-07 20:45 ` gratian.crisan at ni dot com
2014-10-02 21:57 ` davidh at realtimeint dot com
2014-10-06  7:57 ` triegel at redhat dot com
2020-07-06 14:05 ` carlos at redhat dot com
2021-08-23 13:32 ` will at eccles dot dev
2021-09-18 18:55 ` laurettastokes89 at gmail dot com
2021-10-21 15:42 ` fweimer at redhat dot com
2010-05-11 18:46 [Bug nptl/11588] New: " dvhltc at us dot ibm dot com
2010-05-11 18:48 ` [Bug nptl/11588] " dvhltc at us dot ibm dot com
2010-05-11 18:50 ` dvhltc at us dot ibm dot com
2010-05-11 18:51 ` dvhltc at us dot ibm dot com
2010-05-11 18:56 ` dvhltc at us dot ibm dot com
2010-05-12  5:02 ` dino at in dot ibm dot com
2010-05-12 11:06 ` pasky at suse dot cz
2010-05-13  1:55 ` dvhltc at us dot ibm dot com
2010-05-13  8:03 ` dvhltc at us dot ibm dot com
2010-05-13  8:05 ` dvhltc at us dot ibm dot com
2010-05-13  8:07 ` dvhltc at us dot ibm dot com
2010-05-13  8:08 ` dvhltc at us dot ibm dot com
2010-05-13  8:11 ` dvhltc at us dot ibm dot com
2010-05-13  8:13 ` dvhltc at us dot ibm dot com
2010-05-13 18:45 ` dvhltc at us dot ibm dot com
2010-05-27 23:19 ` dvhltc at us dot ibm dot com
2010-05-28 20:35 ` dvhltc at us dot ibm dot com
2010-06-17 20:59 ` dvhltc at us dot ibm dot com
2010-06-17 22:17 ` tglx at linutronix dot de

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=bug-11588-131-ZuVpXowMkk@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).