From owner-freebsd-bugs@FreeBSD.ORG  Wed Oct  3 15:00:27 2012
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 7D06F106564A
	for <freebsd-bugs@hub.freebsd.org>;
	Wed,  3 Oct 2012 15:00:27 +0000 (UTC)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 683258FC08
	for <freebsd-bugs@hub.freebsd.org>;
	Wed,  3 Oct 2012 15:00:27 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q93F0Rv3034154
	for <freebsd-bugs@freefall.freebsd.org>; Wed, 3 Oct 2012 15:00:27 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q93F0RHa034153;
	Wed, 3 Oct 2012 15:00:27 GMT (envelope-from gnats)
Date: Wed, 3 Oct 2012 15:00:27 GMT
Message-Id: <201210031500.q93F0RHa034153@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Andriy Gapon <avg@FreeBSD.org>
Cc: 
Subject: Re: kern/172166: Deadlock in the networking code, possible due to
 a bug in the SCHED_ULE
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Andriy Gapon <avg@FreeBSD.org>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2012 15:00:27 -0000

The following reply was made to PR kern/172166; it has been noted by GNATS.

From: Andriy Gapon <avg@FreeBSD.org>
To: bug-followup@FreeBSD.org
Cc: Alexander Motin <mav@FreeBSD.org>, eugen@eg.sd.rdtc.ru
Subject: Re: kern/172166: Deadlock in the networking code, possible due to
 a bug in the SCHED_ULE
Date: Wed, 03 Oct 2012 17:56:39 +0300

 on 02/10/2012 09:58 Alexander Motin said the following:
 > About rw_lock priority propagation locking(9) tells:
 > The rw_lock locks have priority propagation like mutexes, but priority can be
 > propagated only to an exclusive holder.  This limitation comes from the fact that
 > shared owners are anonymous.
 
 Yeah... and as we see it has a potential to result in priority inversion.
 
 > What's about idle stealing threshold, it was fixed in HEAD at r239194, but wasn't
 > merged yet. It should be trivial to merge it.
 
 And I've also misread the code, confused 6 CPUs case with 8 CPUs case.
 
 
 -- 
 Andriy Gapon