From owner-freebsd-bugs@freebsd.org  Thu Sep  7 18:43:08 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 181FFE07F18
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu,  7 Sep 2017 18:43:08 +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 8B94E726E0
 for <freebsd-bugs@FreeBSD.org>; Thu,  7 Sep 2017 18:43:07 +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 v87Ih7N9005674
 for <freebsd-bugs@FreeBSD.org>; Thu, 7 Sep 2017 18:43:07 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 222126] pf is not clearing expired states
Date: Thu, 07 Sep 2017 18:43:07 +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.1-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: cc
Message-ID: <bug-222126-8-seND8iIKDn@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-222126-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-222126-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: Thu, 07 Sep 2017 18:43:08 -0000

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

Kristof Provost <kp@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kp@freebsd.org

--- Comment #1 from Kristof Provost <kp@freebsd.org> ---
I don't think I've seen that before.

Do you have a non-default kernel config? (I'm especially interested in know=
ing
if you're running VIMAGE, but any non-default settings are interesting to k=
now
about)

Can you check if the pf purge thread is running? ('[pf purge'])

Please also give this dtrace script a quick try:

#!/usr/sbin/dtrace -s

fbt:pf:pf_purge_expired_states:entry
{

}

fbt:pf:pf_purge_expired_states:return
{

}

fbt:pf:pf_purge_unlinked_rules:entry
{

}

fbt:pf:pf_purge_unlinked_rules:return
{

}

fbt:pf:pf_purge_expired_fragments:entry
{

}

fbt:pf:pf_purge_expired_src_nodes:entry
{

}

fbt:pf:pf_purge_expired_src_nodes:return
{

}

fbt:pf:pf_purge_thread:entry
{

}

It should show us if the purge code is running or not.

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