From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glibc-bugs-return-5647-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Received: (qmail 10296 invoked by alias); 8 Nov 2006 09:31:46 -0000
Received: (qmail 10221 invoked by uid 48); 8 Nov 2006 09:31:39 -0000
Date: Wed, 08 Nov 2006 09:31:00 -0000
From: "loic-dev at gmx dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Message-ID: <20061108093138.3482.loic-dev@gmx.net>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug nptl/3482] New: pthread_cond_signal does not respect thread priority
X-Bugzilla-Reason: CC
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
X-SW-Source: 2006-11/txt/msg00026.txt.bz2
List-Id: <glibc-bugs.sourceware.org>

If two threads with different priorities are waiting on the same condition 
variable, a pthread_cond_signal() on that condvar shall wake the thread 
waiting the longest on the condvar, not the one with the highest priority. As 
of my understanding, this departs from SUS.

-- 
           Summary: pthread_cond_signal does not respect thread priority
           Product: glibc
           Version: 2.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
        AssignedTo: drepper at redhat dot com
        ReportedBy: loic-dev at gmx dot net
                CC: glibc-bugs at sources dot redhat dot com


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.