This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/5192] Internal lock in pthread struct is vulnerable to priority inversion
- From: "spcurry5 at linux dot vnet dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 25 Apr 2008 01:26:44 -0000
- Subject: [Bug nptl/5192] Internal lock in pthread struct is vulnerable to priority inversion
- References: <20071017151048.5192.matt.hoosier@gmail.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From spcurry5 at linux dot vnet dot ibm dot com 2008-04-25 01:26 -------
I have a few points worth noting:
(1) I was unable to find anywhere in the POSIX specification that states the
per-thread mutex must not cause a priority inversion.
(2) Changing the pthread implementation so that every thread has a
priority-inheritance mutex, instead of a standard mutex, would cause some
performance loss due to the extra overhead associated with using
priority-inheritance mutexes.
(3) The priority inversion situation you have described does not cause any of
the threads to hold onto a resource indefinitely, thereby preventing some other
thread from ever making forward progress. All threads eventually make forward
progress, therefore, this is more of a performance issue than a correctness
issue. So I am marking this bug as an enhancement.
--
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
http://sourceware.org/bugzilla/show_bug.cgi?id=5192
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.