From owner-freebsd-current Mon Jun 14 21:17: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 6F09B14DAE for ; Mon, 14 Jun 1999 21:17:06 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id AAA37420; Tue, 15 Jun 1999 00:15:27 -0400 (EDT) Date: Tue, 15 Jun 1999 00:15:27 -0400 (EDT) From: Chuck Robey To: Matthew Dillon Cc: "David E. Cross" , David Scheidt , Chan Yiu Wah , freebsd-current@FreeBSD.ORG, "David E. Cross" Subject: Re: What happened to CTM src-cur? In-Reply-To: <199906150355.UAA14268@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 14 Jun 1999, Matthew Dillon wrote: > Ack, you may have opened up a can of worms here. I don't even think > that nfs_namei() does the right thing when it returns an error... it > doesn't look like it clears the ndp->ni_vp either in some error cases. > > We are going to have to instrument the code - basically means NULLing > out ni_vp and any local vnode pointer when the vnode in question is > released so we can keep track of it and putting KASSERT()s in strategic > places. nfs_namei() in nfs/nfs_subs.c and just about all the subroutines > defined in nfs/nfs_serv.c. OK, you hijacked my thread ... OK, I've done worse, but please, could you change the subject line? We *do* still have a ctm outage here, it's clearing up (I hope) but I want feedback, and you've prevented it. > > -Matt > Matthew Dillon > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message