From owner-freebsd-dtrace@freebsd.org  Sat Oct 27 22:40:40 2018
Return-Path: <owner-freebsd-dtrace@freebsd.org>
Delivered-To: freebsd-dtrace@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1848F10D6727
 for <freebsd-dtrace@mailman.ysv.freebsd.org>;
 Sat, 27 Oct 2018 22:40:40 +0000 (UTC)
 (envelope-from longwitz@incore.de)
Received: from dss.incore.de (dss.incore.de [195.145.1.138])
 (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 A9F197E78E
 for <freebsd-dtrace@freebsd.org>; Sat, 27 Oct 2018 22:40:39 +0000 (UTC)
 (envelope-from longwitz@incore.de)
Received: from inetmail.dmz (inetmail.dmz [10.3.0.3])
 by dss.incore.de (Postfix) with ESMTP id 83A53139AF
 for <freebsd-dtrace@freebsd.org>; Sun, 28 Oct 2018 00:40:38 +0200 (CEST)
X-Virus-Scanned: amavisd-new at incore.de
Received: from dss.incore.de ([10.3.0.3])
 by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024)
 with LMTP id CAj9bAJf2MNy for <freebsd-dtrace@freebsd.org>;
 Sun, 28 Oct 2018 00:40:37 +0200 (CEST)
Received: from mail.local.incore (fwintern.dmz [10.0.0.253])
 by dss.incore.de (Postfix) with ESMTP id 8462E139AC
 for <freebsd-dtrace@freebsd.org>; Sun, 28 Oct 2018 00:40:37 +0200 (CEST)
Received: from bsdmhs.longwitz (unknown [192.168.99.6])
 by mail.local.incore (Postfix) with ESMTP id 701C011F
 for <freebsd-dtrace@freebsd.org>; Sun, 28 Oct 2018 00:40:37 +0200 (CEST)
Message-ID: <5BD4E965.9040006@incore.de>
Date: Sun, 28 Oct 2018 00:40:37 +0200
From: Andreas Longwitz <longwitz@incore.de>
User-Agent: Thunderbird 2.0.0.19 (X11/20090113)
MIME-Version: 1.0
To: "freebsd-dtrace@freebsd.org" <freebsd-dtrace@freebsd.org>
Subject: Why my DTrace script does not work after installing a new kernel
 without reboot
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-dtrace@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A discussion list for developers working on DTrace in FreeBSD."
 <freebsd-dtrace.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-dtrace>, 
 <mailto:freebsd-dtrace-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-dtrace/>
List-Post: <mailto:freebsd-dtrace@freebsd.org>
List-Help: <mailto:freebsd-dtrace-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace>,
 <mailto:freebsd-dtrace-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Oct 2018 22:40:40 -0000

I have a simple, probably stupid question. I run FreeBSD 10.4 Stable
r338093 and use the script

#!/usr/sbin/dtrace -s

dtrace:::BEGIN
{
printf("pf_default_rule.timeout[2/16/17]=%d/%d/%d\n",
  kernel`pf_default_rule.timeout[2], kernel`pf_default_rule.timeout[16],
  kernel`pf_default_rule.timeout[17]);
}

The output normally is
  pf_default_rule.timeout[2/16/17]=86400/6000/12000

But when I change the sourcefile /sys/netpfil/pf/pf.c trying a patch and
build and install the new kernel but without reboot, then the output of
the script is wrong:

  pf_default_rule.timeout[2/16/17]=3237216124/0/0

After reboot everything works again.

-- 
Andreas Longwitz