From owner-freebsd-bugs@freebsd.org  Sat Jun 24 09:22:53 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1175BD9B541
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat, 24 Jun 2017 09:22:53 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id F3F1E36C4
 for <freebsd-bugs@FreeBSD.org>; Sat, 24 Jun 2017 09:22:52 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v5O9MqS7001439
 for <freebsd-bugs@FreeBSD.org>; Sat, 24 Jun 2017 09:22:52 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 220217] deadlock on enc and pf
Date: Sat, 24 Jun 2017 09:22:53 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kp@freebsd.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-220217-8-yMQwibPtHj@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-220217-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-220217-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/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: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jun 2017 09:22:53 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220217

--- Comment #3 from Kristof Provost <kp@freebsd.org> ---
(In reply to vegeta from comment #2)
There is no other thread. We assert that 'rw_wowner(rw) !=3D curthread', so=
 the
thread holding the lock must not be the current thread (trying to acquire t=
he
lock).

That assertion fails, so we are the thread holding the lock, yet we try to =
lock
again.

That seems to be in tcp_timer_rexmt(). It holds a write lock on the struct
inpcb, so when pf goes to look up the inpcb and tries to get a read lock we=
 run
into this assertion failure. (tcp_output() in fact asserts that the inpcb m=
ust
be write locked when it's called.)

I'm not quite sure how to fix this though. In fact, right now I don't
understand how this ever works.

--=20
You are receiving this mail because:
You are the assignee for the bug.=