From owner-cvs-src@FreeBSD.ORG  Tue Jul  1 08:52:11 2003
Return-Path: <owner-cvs-src@FreeBSD.ORG>
Delivered-To: cvs-src@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 551B837B401; Tue,  1 Jul 2003 08:52:11 -0700 (PDT)
Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 951C943FDF; Tue,  1 Jul 2003 08:52:10 -0700 (PDT)
	(envelope-from mtm@FreeBSD.org)
Received: from repoman.freebsd.org (localhost [127.0.0.1])
	by repoman.freebsd.org (8.12.6/8.12.6) with ESMTP id h61FqA0U036152;
	Tue, 1 Jul 2003 08:52:10 -0700 (PDT)
	(envelope-from mtm@repoman.freebsd.org)
Received: (from mtm@localhost)
	by repoman.freebsd.org (8.12.6/8.12.6/Submit) id h61Fq91e036148;
	Tue, 1 Jul 2003 08:52:09 -0700 (PDT)
Message-Id: <200307011552.h61Fq91e036148@repoman.freebsd.org>
From: Mike Makonnen <mtm@FreeBSD.org>
Date: Tue, 1 Jul 2003 08:52:09 -0700 (PDT)
To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org,
	cvs-all@FreeBSD.org
X-FreeBSD-CVS-Branch: HEAD
Subject: cvs commit: src/lib/libthr/thread thr_mutex.c
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jul 2003 15:52:11 -0000

mtm         2003/07/01 08:52:09 PDT

  FreeBSD src repository

  Modified files:
    lib/libthr/thread    thr_mutex.c 
  Log:
  Do not attempt to reque a thread on a mutex queue. It may be that
  a thread receives a spurious wakeup from sigtimedwait(), so make sure
  that the call to the queueing code is called only once before entering
  the loop (not in the loop). This should fix some fatal errors people
  are seeing with messages stating the thread is already on the mutex queue.
  These errors may still be triggered from signal handlers; however, since
  that part of the code is not locked down yet.
  
  Revision  Changes    Path
  1.14      +1 -1      src/lib/libthr/thread/thr_mutex.c