From owner-freebsd-bugs  Mon Apr  9 21:45:16 2001
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 56BA637B422; Mon,  9 Apr 2001 21:45:14 -0700 (PDT)
	(envelope-from deischen@FreeBSD.org)
Received: (from deischen@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f3A4jEa44256;
	Mon, 9 Apr 2001 21:45:14 -0700 (PDT)
	(envelope-from deischen)
Date: Mon, 9 Apr 2001 21:45:14 -0700 (PDT)
From: <deischen@FreeBSD.org>
Message-Id: <200104100445.f3A4jEa44256@freefall.freebsd.org>
To: Heikki.Tuuri@innobase.inet.fi, deischen@FreeBSD.org,
	freebsd-bugs@FreeBSD.org
Subject: Re: kern/26247: Does pthread_mutex_trylock really work on the latest FreeBSD release if the mutex is already reserved?
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: Does pthread_mutex_trylock really work on the latest FreeBSD release if the mutex is already reserved?

State-Changed-From-To: open->closed
State-Changed-By: deischen
State-Changed-When: Mon Apr 9 21:41:37 PDT 2001
State-Changed-Why: 
This was really an application bug, not a bug in the threads
library.  The application had a low priority thread that held
a mutex needed by a higher priority thread.  The higher priority
thread kept spinning (pthread_mutex_trylock) waiting for the
lower priority thread to release the mutex.  The lower priority
thread got starved and never got a chance to run.

http://www.freebsd.org/cgi/query-pr.cgi?pr=26247

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message