From owner-freebsd-hackers Sat Feb 13 01:41:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA17814 for freebsd-hackers-outgoing; Sat, 13 Feb 1999 01:41:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17806 for ; Sat, 13 Feb 1999 01:41:37 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.2/8.9.1) id BAA14698; Sat, 13 Feb 1999 01:41:37 -0800 (PST) (envelope-from dillon) Date: Sat, 13 Feb 1999 01:41:37 -0800 (PST) From: Matthew Dillon Message-Id: <199902130941.BAA14698@apollo.backplane.com> To: hackers@FreeBSD.ORG Subject: NFS VOP calls (was Re: Lots of "panic: vrele: negative ref cnt" ) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like there are a number of problems, but the one reported above is the only one that gets 'hit'. The NFS code pretty much ignores the VOP semantics for freeing path name elements but it just happens to get called with the path name (cnp) structure flagged the way it happens to decide to use it, so it works. But there is probably some leakage of NAMEI nodes when NFS errors occur. I've only committed the fix for the vrele panic to -3.x. The fix to the rest of the mis-used path elements has been committed to -4.x and will not be backported to -3.x until after the release since I'm not 100% sure those other fixes are correct. -3.x should not be detrimentally effected by not having the other junk in. Confused yet? :-) -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message