From: Yichong Chen <chenyichong@uniontech.com>
To: linkinjeon@kernel.org, sj1557.seo@samsung.com
Cc: yuezhang.mo@sony.com, exfat@lists.linux.dev,
linux-kernel@vger.kernel.org,
Yichong Chen <chenyichong@uniontech.com>
Subject: [PATCH] exfat: clean up new entry on add entry failure
Date: Tue, 28 Jul 2026 13:55:04 +0800 [thread overview]
Message-ID: <20260728055504.412284-1-chenyichong@uniontech.com> (raw)
exfat_add_entry() initializes a new directory entry set before writing
it with exfat_put_dentry_set(). If the write fails, mkdir/create returns
an error but a partially written entry may be left behind.
For non-zero-size directories, the failure also happens after a cluster
has been allocated for the new directory. That cluster needs to be
released if the mkdir fails.
Clean up the new entry best-effort and free the newly allocated directory
cluster when one was allocated.
Signed-off-by: Yichong Chen <chenyichong@uniontech.com>
---
fs/exfat/namei.c | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/fs/exfat/namei.c b/fs/exfat/namei.c
index 038bc6fed681..7bd745090f92 100644
--- a/fs/exfat/namei.c
+++ b/fs/exfat/namei.c
@@ -471,6 +471,7 @@ static int exfat_add_entry(struct inode *inode, const char *path,
struct exfat_entry_set_cache es;
int clu_size = 0;
unsigned int start_clu = EXFAT_FREE_CLUSTER;
+ bool dir_allocated = false;
ret = exfat_resolve_path(inode, path, &uniname);
if (ret)
@@ -497,6 +498,7 @@ static int exfat_add_entry(struct inode *inode, const char *path,
}
start_clu = clu.dir;
clu_size = sbi->cluster_size;
+ dir_allocated = true;
}
/* update the directory entry */
@@ -507,8 +509,16 @@ static int exfat_add_entry(struct inode *inode, const char *path,
exfat_init_ext_entry(&es, num_entries, &uniname, NULL, 0);
ret = exfat_put_dentry_set(&es, IS_DIRSYNC(inode));
- if (ret)
+ if (ret) {
+ if (!exfat_get_dentry_set(&es, sb, &info->dir, dentry,
+ ES_ALL_ENTRIES)) {
+ exfat_remove_entries(inode, &es, ES_IDX_FILE, false);
+ exfat_put_dentry_set(&es, false);
+ }
+ if (dir_allocated)
+ exfat_free_cluster(inode, &clu);
goto out;
+ }
info->entry = dentry;
info->flags = ALLOC_NO_FAT_CHAIN;
--
2.51.0
next reply other threads:[~2026-07-28 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 5:55 Yichong Chen [this message]
2026-07-28 8:49 ` Namjae Jeon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260728055504.412284-1-chenyichong@uniontech.com \
--to=chenyichong@uniontech.com \
--cc=exfat@lists.linux.dev \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=yuezhang.mo@sony.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®