From owner-cvs-all  Sat Feb 13 01:47:33 1999
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA18475
          for cvs-all-outgoing; Sat, 13 Feb 1999 01:47:33 -0800 (PST)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA18470;
          Sat, 13 Feb 1999 01:47:32 -0800 (PST)
          (envelope-from dillon@FreeBSD.org)
From: Matt Dillon <dillon@FreeBSD.ORG>
Received: (from dillon@localhost)
	by freefall.freebsd.org (8.9.2/8.9.2) id BAA13456;
	Sat, 13 Feb 1999 01:47:31 -0800 (PST)
	(envelope-from dillon@FreeBSD.org)
Date: Sat, 13 Feb 1999 01:47:31 -0800 (PST)
Message-Id: <199902130947.BAA13456@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG
Subject: cvs commit: src/sys/nfs nfs_vnops.c
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

dillon      1999/02/13 01:47:31 PST

  Modified files:
    sys/nfs              nfs_vnops.c 
  Log:
      General additional cleanup of VOP API for NFS ops - mainly NFS ignoring
      the API for freeing up cnp's.  This cleanup should not effect nominal
      operation one way or the other since NFS VOPs just happen to be called
      with flags that match what it actually does to the NAMEI components it
      gets.  Still, if an NFS error occured, there was probably some memory
      leakage of NAMEI components with certain NFS VOP ops.
  
  Revision  Changes    Path
  1.122     +13 -4     src/sys/nfs/nfs_vnops.c

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message