From owner-freebsd-hackers  Sat Feb 13 00:57:51 1999
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id AAA14315
          for freebsd-hackers-outgoing; Sat, 13 Feb 1999 00:57:51 -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 AAA14309
          for <hackers@FreeBSD.ORG>; Sat, 13 Feb 1999 00:57:50 -0800 (PST)
          (envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.2/8.9.1) id AAA14274;
	Sat, 13 Feb 1999 00:57:49 -0800 (PST)
	(envelope-from dillon)
Date: Sat, 13 Feb 1999 00:57:49 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199902130857.AAA14274@apollo.backplane.com>
To: hackers@FreeBSD.ORG
Subject: VOP_REMOVE() rules for freeing a_cnp ?
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

    I can't make heads or tails of the VOP_REMOVE() rules for freeing
    a_cnp.

    The man page doesn't say anything about having to free cnp.

    ufs_remove() doesn't bother.

    nfs_remove() always frees it.

    And the unlink() system call seems to expect the cnp to be freed
    by the VOP_REMOVE() function.

    Typically the rule for freeing a struct componentname in a VOP
    routine is 'free it if you return an error, otherwise only free
    it if the SAVESTART flag is not set in cn_flags'.

    I would appreciate it if a VFS guru could look at this junk and
    tell me whos right.

					Matthew Dillon 
					<dillon@backplane.com>

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