From owner-freebsd-hackers@FreeBSD.ORG  Sun Feb  5 18:32:53 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 626CC106564A;
	Sun,  5 Feb 2012 18:32:53 +0000 (UTC)
	(envelope-from deischen@freebsd.org)
Received: from mail.netplex.net (mail.netplex.net [204.213.176.10])
	by mx1.freebsd.org (Postfix) with ESMTP id 101A68FC13;
	Sun,  5 Feb 2012 18:32:52 +0000 (UTC)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
	by mail.netplex.net (8.14.4/8.14.4/NETPLEX) with ESMTP id
	q15IWgR5014601; Sun, 5 Feb 2012 13:32:42 -0500
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.2.6 (mail.netplex.net [204.213.176.10]);
	Sun, 05 Feb 2012 13:32:43 -0500 (EST)
Date: Sun, 5 Feb 2012 13:32:42 -0500 (EST)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: Ivan Voras <ivoras@freebsd.org>
In-Reply-To: <CAF-QHFVADLkduLH1AG_hSZeDtDVCC=FkqZxbxrsMY3Y3+sMZ8A@mail.gmail.com>
Message-ID: <Pine.GSO.4.64.1202051330020.28531@sea.ntplx.net>
References: <jejrbe$or8$1@dough.gmane.org> <201201110806.30620.jhb@freebsd.org>
	<CAF-QHFWFvYTPeM68Mk+OYVX--MNhKOJ2o1GF9ZOsBmtiC5fYFQ@mail.gmail.com>
	<CAGH67wRsek2-WY_ETW6QEER1r5dDXLXfDjbzpHMjtv059Y8cJw@mail.gmail.com>
	<5D37298B-9D68-4F0F-8AAB-E8F2DBB9D9C3@transactionware.com>
	<CAGH67wT3HuxPHUXeTib0qJNH+O5snn3Eiim1bfj8LewYoKdXdA@mail.gmail.com>
	<CAF-QHFVADLkduLH1AG_hSZeDtDVCC=FkqZxbxrsMY3Y3+sMZ8A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: MULTIPART/Mixed; boundary=14dae93b58c8148ec504b83654c2
Content-ID: <Pine.GSO.4.64.1202051330021.28531@sea.ntplx.net>
Cc: Garrett Cooper <yanegomi@gmail.com>, freebsd-hackers@freebsd.org,
	Xin LI <delphij@delphij.net>, davidxu@freebsd.org,
	Jan Mikkelsen <janm-freebsd-hackers@transactionware.com>
Subject: Re: sem(4) lockup in python?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2012 18:32:53 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--14dae93b58c8148ec504b83654c2
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-ID: <Pine.GSO.4.64.1202051330022.28531@sea.ntplx.net>

On Sun, 5 Feb 2012, Ivan Voras wrote:

> On 5 February 2012 11:44, Garrett Cooper <yanegomi@gmail.com> wrote:
>
>>
>> =C2=A0 =C2=A0'make MAKE_JOBS_NUMBER=3D1' is the workground used right no=
w..
>
> David Xu suggested that it is a bug in Python - it doesn't set
> process-shared attribute when it calls sem_init(), but i've tried
> patching it (replacing the port patchfile file the one I've attached)
> and I still get the hang.

I don't understand how process shared semaphores can work.  Perhaps
I'm dumb and ignorant, but a sem_id_t is an allocated struct.   The
actual kernel sem_id is inside the struct.  Isn't this the same
reason pthread_mutex_t and pthread_cond_t cannot be process-shared?

--=20
DE
--14dae93b58c8148ec504b83654c2--