From: Hungyu Lin <dennylin0707@gmail.com>
To: hirofumi@mail.parknet.co.jp
Cc: akpm@linux-foundation.org, brauner@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
dennylin0707@gmail.com
Subject: [PATCH v2] fat: fix parent link count when replacing a sibling directory
Date: Thu, 29 Oct 2026 20:23:52 +0000 [thread overview]
Message-ID: <20261029202352.59890-1-dennylin0707@gmail.com> (raw)
vfat_rename() and do_msdos_rename() adjust parent link counts only when
updating the dotdot entry for a move between different parents. Replacing
an existing empty directory in the same parent also removes a
subdirectory, but leaves the parent's link count unchanged.
For example, renaming one of two sibling directories over the other
leaves the parent with four links instead of three. stat and ls report
the stale count, and find -links 3 does not match the parent.
Drop the parent's link count for this case after the source entry has
been removed successfully. Leave cross-parent renames, regular files
and the existing error paths unchanged.
As in rmdir, check that the parent's link count is at least three before
decrementing it. Report a filesystem error if corrupted directory entries
have left the count too low, rather than reducing it below two.
Acked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Signed-off-by: Hungyu Lin <dennylin0707@gmail.com>
---
Changes in v2:
- Check the parent link count before decrementing it and report low
counts with fat_fs_error(), matching rmdir(), as noted by Sashiko.
- Retain Hirofumi's Acked-by from v1.
v1: https://lore.kernel.org/r/20261028211626.26103-1-dennylin0707@gmail.com
Review: https://sashiko.dev/#/patchset/20261028211626.26103-1-dennylin0707@gmail.com
fs/fat/namei_msdos.c | 8 ++++++++
fs/fat/namei_vfat.c | 8 ++++++++
2 files changed, 16 insertions(+)
diff --git a/fs/fat/namei_msdos.c b/fs/fat/namei_msdos.c
index c7500c2859e0..97289c9d9261 100644
--- a/fs/fat/namei_msdos.c
+++ b/fs/fat/namei_msdos.c
@@ -565,6 +565,14 @@ static int do_msdos_rename(struct inode *old_dir, unsigned char *old_name,
(void)sync_inode_metadata(old_dir, 1);
if (new_inode) {
+ if (is_dir && old_dir == new_dir) {
+ if (old_dir->i_nlink >= 3)
+ drop_nlink(old_dir);
+ else
+ fat_fs_error(old_dir->i_sb,
+ "parent dir link count too low (%u)",
+ old_dir->i_nlink);
+ }
drop_nlink(new_inode);
if (is_dir)
drop_nlink(new_inode);
diff --git a/fs/fat/namei_vfat.c b/fs/fat/namei_vfat.c
index ff7652bf0410..c4d5628c05fa 100644
--- a/fs/fat/namei_vfat.c
+++ b/fs/fat/namei_vfat.c
@@ -1011,6 +1011,14 @@ static int vfat_rename(struct inode *old_dir, struct dentry *old_dentry,
vfat_update_dir_metadata(old_dir, &ts);
if (new_inode) {
+ if (is_dir && old_dir == new_dir) {
+ if (old_dir->i_nlink >= 3)
+ drop_nlink(old_dir);
+ else
+ fat_fs_error(old_dir->i_sb,
+ "parent dir link count too low (%u)",
+ old_dir->i_nlink);
+ }
drop_nlink(new_inode);
if (is_dir)
drop_nlink(new_inode);
--
2.43.0
next reply other threads:[~2026-10-29 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 20:23 Hungyu Lin [this message]
2026-10-30 4:31 ` OGAWA Hirofumi
2026-10-30 4:34 ` OGAWA Hirofumi
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=20261029202352.59890-1-dennylin0707@gmail.com \
--to=dennylin0707@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®