Date: Tue, 15 Jun 1999 00:15:27 -0400 (EDT) From: Chuck Robey <chuckr@picnic.mat.net> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: "David E. Cross" <crossd@cs.rpi.edu>, David Scheidt <dscheidt@enteract.com>, Chan Yiu Wah <c5666305@hkstar.com>, freebsd-current@FreeBSD.ORG, "David E. Cross" <crossd@cs.rpi.edu> Subject: Re: What happened to CTM src-cur? Message-ID: <Pine.BSF.4.10.9906150013460.567-100000@picnic.mat.net> In-Reply-To: <199906150355.UAA14268@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 > <dillon@backplane.com> > ----------------------------+----------------------------------------------- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9906150013460.567-100000>