This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: malloc/free and priority inheritance?
- From: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>
- To: Stanislav Meduna <stano at meduna dot org>
- Cc: libc-help <libc-help at sourceware dot org>, "linux-rt-users at vger dot kernel dot org" <linux-rt-users at vger dot kernel dot org>
- Date: Thu, 4 Apr 2013 21:09:57 +0530
- Subject: Re: malloc/free and priority inheritance?
- References: <515B647C dot 3080505 at meduna dot org> <515D7943 dot 5000401 at meduna dot org> <515D808C dot 8090808 at meduna dot org> <CAAHN_R1zLdHqpC4JGxjJtADRWGA0hC=G2C3=0Z21KTKk5HJNtg at mail dot gmail dot com> <515D97B8 dot 5030101 at meduna dot org>
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.
Siddhesh
--
http://siddhesh.in