summaryrefslogtreecommitdiff
path: root/components
diff options
context:
space:
mode:
authorδΈŽιžη†Š <[email protected]>2026-07-12 17:19:07 +0800
committerRbb666 <[email protected]>2026-07-13 10:54:07 +0800
commit63b4a7fcc2971b2f3001853da9fe33207dd80906 (patch)
treed078746768644818f9c3d0c82ead2618d79b0790 /components
parentcf1c12ee06f816e12defed94d8450f14e876a31e (diff)
[chg][dfs]Clean up comments in dfs_elm_free_vnode
Removed unnecessary comments from dfs_elm_free_vnode function.
Diffstat (limited to 'components')
-rw-r--r--components/dfs/dfs_v2/filesystems/elmfat/dfs_elm.c8
1 files changed, 0 insertions, 8 deletions
diff --git a/components/dfs/dfs_v2/filesystems/elmfat/dfs_elm.c b/components/dfs/dfs_v2/filesystems/elmfat/dfs_elm.c
index fcb05dd48a..4d4de5e123 100644
--- a/components/dfs/dfs_v2/filesystems/elmfat/dfs_elm.c
+++ b/components/dfs/dfs_v2/filesystems/elmfat/dfs_elm.c
@@ -1018,14 +1018,6 @@ static struct dfs_vnode *dfs_elm_create_vnode(struct dfs_dentry *dentry, int typ
static int dfs_elm_free_vnode(struct dfs_vnode *vnode)
{
- /* free_vnode is the backstop destruction point: called from
- dfs_vnode_unref when ref_count drops to 0, and from dfs_vnode_destroy on
- a create/lookup failure (ref_count == 1). Normally dfs_elm_close has
- already released the resource and set data = NULL, so this is a no-op.
- It only tears down the resource when close bailed out early due to
- ref_count > 1 (a transient lookup had raised it), which is exactly the
- leak this guards against. data != NULL means the resource is still
- live and the lock is still initialized, so both are released here. */
if (vnode && vnode->ref_count <= 1 && vnode->data != RT_NULL)
{
if (vnode->type == FT_DIRECTORY)