From: Darren Hart <dvhart@linux.intel.com>
To: Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>
Cc: Stanislav Meduna <stano@meduna.org>,
libc-help <libc-help@sourceware.org>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: malloc/free and priority inheritance?
Date: Fri, 05 Apr 2013 10:39:48 -0700 [thread overview]
Message-ID: <515F0C64.20609@linux.intel.com> (raw)
In-Reply-To: <CAAHN_R0oHL+oWxs_0SBwi4dRWM9HDrFM0Y7ZDLZQGNHnnxYzHQ@mail.gmail.com>
On 04/04/2013 08:39 AM, Siddhesh Poyarekar wrote:
> On 4 April 2013 20:39, Stanislav Meduna <stano@meduna.org> wrote:
>> The first thing e.g. the __pthread_cond_broadcast (and most of the
>> other functions as well) does is to grab lll_lock. Is the following
>> scenario possible?
>
> Yes this is possible. I think there is a bug report that describes
> this. We need to convert the pthread_cond_t internal lock into a PI
> one if the mutex guarding it is PI. It's probably tricky to do
> though; I haven't thought it through.
I have patches out on the glibc alpha list that do this. It is on my
plate to dust these off, reapply and test them, and try to push them
again, I just haven't been able to get to it.
Patches and test cases available here:
http://sourceware.org/bugzilla/show_bug.cgi?id=11588
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2013-04-05 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 23:06 malloc/free and priority inheritance? Stanislav Meduna
2013-04-04 12:59 ` Stanislav Meduna
2013-04-04 13:30 ` Stanislav Meduna
2013-04-04 13:37 ` Siddhesh Poyarekar
2013-04-04 14:53 ` Carlos O'Donell
2013-04-04 15:32 ` Siddhesh Poyarekar
2013-04-06 14:24 ` Carlos O'Donell
2013-04-04 15:09 ` Stanislav Meduna
2013-04-04 15:39 ` Siddhesh Poyarekar
2013-04-05 17:39 ` Darren Hart [this message]
2013-04-06 14:27 ` Carlos O'Donell
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=515F0C64.20609@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=libc-help@sourceware.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=siddhesh.poyarekar@gmail.com \
--cc=stano@meduna.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.