From owner-freebsd-hackers@FreeBSD.ORG  Sun Jan 27 12:24:04 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@FreeBSD.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id E8744F72;
 Sun, 27 Jan 2013 12:24:04 +0000 (UTC) (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id B74A6DD9;
 Sun, 27 Jan 2013 12:24:03 +0000 (UTC)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA19523;
 Sun, 27 Jan 2013 14:24:02 +0200 (EET) (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1TzRHF-000JDr-Mc; Sun, 27 Jan 2013 14:24:01 +0200
Message-ID: <51051C61.4060608@FreeBSD.org>
Date: Sun, 27 Jan 2013 14:24:01 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130121 Thunderbird/17.0.2
MIME-Version: 1.0
To: freebsd-hackers@FreeBSD.org
Subject: dtrace vs module unloading
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=X-VIET-VPS
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Jan 2013 12:24:05 -0000


It seems that FreeBSD DTrace currently does not track module loading / unloading
at all.  dtrace_module_loaded/dtrace_module_unloaded are both under ifdef sun.

I think that this is a root cause of e.g. fbt probes for some functions
remaining after a module that provides the functions is unloaded.

It looks like currently we do not post any event when a module gets loaded /
unloaded.  Perhaps this is one of the factors in current situation.
OTOH, in Solaris they just have some dtrace hooks in the form of function
pointers directly in the module handling code (equivalent of our kern_linker).

-- 
Andriy Gapon