Date: Sat, 13 Feb 1999 00:57:49 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: hackers@FreeBSD.ORG Subject: VOP_REMOVE() rules for freeing a_cnp ? Message-ID: <199902130857.AAA14274@apollo.backplane.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902130857.AAA14274>