From owner-freebsd-threads@FreeBSD.ORG  Sun Jul 21 15:16:06 2013
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 328D1BEB
 for <freebsd-threads@freebsd.org>; Sun, 21 Jul 2013 15:16:06 +0000 (UTC)
 (envelope-from deischen@freebsd.org)
Received: from mail.netplex.net (mail.netplex.net [204.213.176.9])
 by mx1.freebsd.org (Postfix) with ESMTP id EE602356
 for <freebsd-threads@freebsd.org>; Sun, 21 Jul 2013 15:16:05 +0000 (UTC)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
 by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r6LFFwqb034851;
 Sun, 21 Jul 2013 11:15:58 -0400
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net)
X-Greylist: Message whitelisted by DRAC access database, not delayed by
 milter-greylist-4.4.1 (mail.netplex.net [204.213.176.9]);
 Sun, 21 Jul 2013 11:15:58 -0400 (EDT)
Date: Sun, 21 Jul 2013 11:15:58 -0400 (EDT)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: Joe Marcus Clarke <marcus@marcuscom.com>
Subject: Re: Mutexes and error checking
In-Reply-To: <51EB5EC4.6050802@marcuscom.com>
Message-ID: <Pine.GSO.4.64.1307211115010.6265@sea.ntplx.net>
References: <51E71D4F.5030502@marcuscom.com>
 <Pine.GSO.4.64.1307181059460.22570@sea.ntplx.net>
 <51E8061B.60906@marcuscom.com>
 <Pine.GSO.4.64.1307181118100.22570@sea.ntplx.net>
 <Pine.GSO.4.64.1307182144030.23634@sea.ntplx.net>
 <Pine.GSO.4.64.1307190152440.25756@sea.ntplx.net>
 <51EB5EC4.6050802@marcuscom.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Koop Mast <kwm@rainbow-runner.nl>, freebsd-threads@freebsd.org
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
 <mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Jul 2013 15:16:06 -0000

On Sun, 21 Jul 2013, Joe Marcus Clarke wrote:

> On 7/19/13 1:55 AM, Daniel Eischen wrote:
>> On Thu, 18 Jul 2013, Daniel Eischen wrote:
>>
>> Ugh!  I misread the problem when I tried to recreate it and
>> test it on Solaris, so forget that last email.
>>
>> It seems Solaris behaves like Linux with PTHREAD_MUTEX_NORMAL
>> and _unlocking_ mutexes owned by other threads (dead or not).
>> Solaris only returns EPERM for PTHREAD_MUTEX_ERRORCHECK
>> mutexes.
>
> Given that, should we do the same?

I'm testing a patch.  Give me a couple of days to get
some more cycles.

-- 
DE