From owner-freebsd-bugs@FreeBSD.ORG  Tue Oct  2 07:00:19 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 D8AA9106566B
	for <freebsd-bugs@hub.freebsd.org>;
	Tue,  2 Oct 2012 07:00:19 +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 B23918FC15
	for <freebsd-bugs@hub.freebsd.org>;
	Tue,  2 Oct 2012 07:00:19 +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 q9270Jdh022671
	for <freebsd-bugs@freefall.freebsd.org>; Tue, 2 Oct 2012 07:00:19 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9270JeN022664;
	Tue, 2 Oct 2012 07:00:19 GMT (envelope-from gnats)
Date: Tue, 2 Oct 2012 07:00:19 GMT
Message-Id: <201210020700.q9270JeN022664@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Alexander Motin <mav@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: Alexander Motin <mav@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: Tue, 02 Oct 2012 07:00:20 -0000

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

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

 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.
 
 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.
 
 -- 
 Alexander Motin