From owner-freebsd-threads@FreeBSD.ORG  Sun Jul 21 15:22:02 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 9D5F4C98;
 Sun, 21 Jul 2013 15:22:02 +0000 (UTC)
 (envelope-from marcus@marcuscom.com)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209])
 by mx1.freebsd.org (Postfix) with ESMTP id 624A138D;
 Sun, 21 Jul 2013 15:22:01 +0000 (UTC)
X-TACSUNS: Virus Scanned
Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1])
 by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6LFM1Pg001235;
 Sun, 21 Jul 2013 11:22:01 -0400 (EDT)
Received: from rtp-jclarke-8916.cisco.com (rtp-jclarke-8916.cisco.com
 [10.117.46.167])
 by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r6LFLwcW001248;
 Sun, 21 Jul 2013 11:21:59 -0400 (EDT)
Message-ID: <51EBFC97.6000504@marcuscom.com>
Date: Sun, 21 Jul 2013 11:21:59 -0400
From: Joe Marcus Clarke <marcus@marcuscom.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Daniel Eischen <deischen@freebsd.org>
Subject: Re: Mutexes and error checking
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>
 <Pine.GSO.4.64.1307211115010.6265@sea.ntplx.net>
In-Reply-To: <Pine.GSO.4.64.1307211115010.6265@sea.ntplx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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
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:22:02 -0000

On 7/21/13 11:15 AM, Daniel Eischen wrote:
> 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.
> 

Thanks!

Joe

-- 
PGP Key : http://www.marcuscom.com/pgp.asc