From 63b4a7fcc2971b2f3001853da9fe33207dd80906 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E4=B8=8E=E9=9D=9E=E7=86=8A?= <38059101+Unbear-Hz@users.noreply.github.com> Date: Sun, 12 Jul 2026 17:19:07 +0800 Subject: [PATCH] [chg][dfs]Clean up comments in dfs_elm_free_vnode Removed unnecessary comments from dfs_elm_free_vnode function. --- components/dfs/dfs_v2/filesystems/elmfat/dfs_elm.c | 8 -------- 1 file changed, 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)