From owner-freebsd-net Sun Sep 23 16:53:26 2001 Delivered-To: freebsd-net@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [64.0.106.45]) by hub.freebsd.org (Postfix) with ESMTP id 219DF37B401 for ; Sun, 23 Sep 2001 16:53:23 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id TAA85217; Sun, 23 Sep 2001 19:53:20 -0400 (EDT) Date: Sun, 23 Sep 2001 19:53:20 -0400 (EDT) From: "Matthew N. Dodd" To: Jonathan Lemon Cc: net@freebsd.org Subject: Re: review request. In-Reply-To: <20010923183909.A79251@prism.flugsvamp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 23 Sep 2001, Jonathan Lemon wrote: > On Sun, Sep 23, 2001 at 07:32:18PM -0400, Matthew N. Dodd wrote: > > On Sun, 23 Sep 2001, Jonathan Lemon wrote: > > > >sys/net/if.c and bpf.c have problems with if_detach() and > > > >bpfdetach() when they are called with a struct ifnet that has not had > > > >if_attach() and bpfattach() called on it. Null pointer reference -> > > > >*boom* etc. > > > > > > I would say that this is to be expected. Why is the system calling > > > the detach functions on a device that isn't attached in the first > > > place? > > > > Driver mistake, but I see no reason why these functions shouldn't handle > > this gracefully. > > Because all it does is conceal the original error. Better to catch > the mistake and fix the driver than paper it over. Right; rather than failing the detach routines will fuss about it so you know exactly how you screwed up. I don't see this papering anything over. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message