public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "spcurry5 at linux dot vnet dot ibm dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/5192] Internal lock in pthread struct is vulnerable to priority inversion Date: Fri, 25 Apr 2008 01:27:00 -0000 [thread overview] Message-ID: <20080425012644.1718.qmail@sourceware.org> (raw) In-Reply-To: <20071017151048.5192.matt.hoosier@gmail.com> ------- 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.
next prev parent reply other threads:[~2008-04-25 1:27 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-17 15:11 [Bug nptl/5192] New: " matt dot hoosier at gmail dot com 2007-10-17 15:52 ` [Bug nptl/5192] " matt dot hoosier at gmail dot com 2007-12-15 9:40 ` ismail at pardus dot org dot tr 2008-04-17 22:55 ` spcurry5 at linux dot vnet dot ibm dot com 2008-04-25 0:28 ` spcurry5 at linux dot vnet dot ibm dot com 2008-04-25 1:27 ` spcurry5 at linux dot vnet dot ibm dot com [this message] 2008-04-25 20:15 ` rsa at us dot ibm dot com 2008-12-30 21:23 ` spcurry5 at linux dot vnet dot ibm dot com [not found] <bug-5192-131@http.sourceware.org/bugzilla/> 2012-12-19 10:42 ` schwab@linux-m68k.org
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=20080425012644.1718.qmail@sourceware.org \ --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: linkBe 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).