From owner-freebsd-pf@FreeBSD.ORG Wed May 7 15:50:01 2014 Return-Path: Delivered-To: freebsd-pf@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4D1569AE for ; Wed, 7 May 2014 15:50:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (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 3955A994 for ; Wed, 7 May 2014 15:50:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s47Fo1HV079893 for ; Wed, 7 May 2014 15:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s47Fo0um079887; Wed, 7 May 2014 15:50:00 GMT (envelope-from gnats) Date: Wed, 7 May 2014 15:50:00 GMT Message-Id: <201405071550.s47Fo0um079887@freefall.freebsd.org> To: freebsd-pf@FreeBSD.org Cc: From: Mathieu Subject: Re: kern/188063: deadlock between syncache(4) and pf(4) Reply-To: Mathieu X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2014 15:50:01 -0000 The following reply was made to PR kern/188063; it has been noted by GNATS. From: Mathieu To: FreeBSD-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/188063: deadlock between syncache(4) and pf(4) Date: Wed, 07 May 2014 11:45:39 -0400 On 3/29/2014 7:10 PM, FreeBSD-gnats-submit@FreeBSD.org wrote: > Thank you very much for your problem report. > It has the internal identification `kern/188063'. > The individual assigned to look at your > report is: freebsd-bugs. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=188063 > >> Category: kern >> Responsible: freebsd-bugs >> Synopsis: deadlock between syncache(4) and pf(4) >> Arrival-Date: Sat Mar 29 23:10:00 UTC 2014 Well, turns out this was caused by pf(4) "user" rules. It's been about a month since I removed them and the server has been running without deadlocking since then. Looks like the "workaround" mentioned in the pf(4) manpage isn't totally safe on 9.X.