From owner-freebsd-net@FreeBSD.ORG  Thu Oct 20 20:01:43 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9AE0A16A41F
	for <freebsd-net@freebsd.org>; Thu, 20 Oct 2005 20:01:43 +0000 (GMT)
	(envelope-from dunstan@freebsd.czest.pl)
Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D107C43D5A
	for <freebsd-net@freebsd.org>; Thu, 20 Oct 2005 20:01:42 +0000 (GMT)
	(envelope-from dunstan@freebsd.czest.pl)
Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4])
	by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id j9KKKaaq004576
	for <freebsd-net@freebsd.org>; Thu, 20 Oct 2005 20:20:36 GMT
	(envelope-from dunstan@freebsd.czest.pl)
Received: (from dunstan@localhost)
	by freebsd.czest.pl (8.12.10/8.12.9/Submit) id j9KKKZnY004575
	for freebsd-net@freebsd.org; Thu, 20 Oct 2005 20:20:35 GMT
	(envelope-from dunstan)
Date: Thu, 20 Oct 2005 20:20:34 +0000
From: "Wojciech A. Koszek" <dunstan@freebsd.czest.pl>
To: freebsd-net@freebsd.org
Message-ID: <20051020202034.GA4556@freebsd.czest.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Subject: Dependency between interfaces
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2005 20:01:43 -0000

Hello,

Is EVENTHANDLER(9) proper way of notification for standalone driver about
network interface attach/detach operations? I've met simple problem in
ef(4), which causes machine freeze in following situation: load NIC driver
-> load if_ef -> unload NIC driver -> some activity with interface.
Althought driver of network interface no longer exists, if_ef does not know
about it and continues it's operation.

I've seen similar situation for example in ng_fec(4): piece of code needs to
call some cleanup routines in order to keep pointers in valid state. I think
this situation is almost the same like this current in if_bridge(4). Just
repeat situation described above for ef(4), but with if_bridge(4).

Regards,
-- 
* Wojciech A. Koszek && dunstan@FreeBSD.czest.pl