public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sungjong Seo" <sj1557.seo@samsung.com>
To: "'Chi Zhiling'" <chizhiling@163.com>,
	"'Namjae Jeon'" <linkinjeon@kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"'Chi Zhiling'" <chizhiling@kylinos.cn>, <cpgs@samsung.com>,
	<sj1557.seo@samsung.com>
Subject: RE: [PATCH v2 3/6] exfat: use exfat_fat_walk helper to simplify fat entry walking
Date: Thu, 2 Apr 2026 23:22:23 +0900	[thread overview]
Message-ID: <015c01dcc2ac$1ffd7520$5ff85f60$@samsung.com> (raw)
In-Reply-To: <20260401071138.114836-4-chizhiling@163.com>

Hi, Chi Zhiling,
> Replace the custom exfat_walk_fat_chain() function and open-coded FAT 
> chain walking logic with the exfat_fat_walk() helper across 
> exfat_find_location, __exfat_get_dentry_set, and exfat_map_cluster.
> 
> Signed-off-by: Chi Zhiling <chizhiling@kylinos.cn>
> ---
>  fs/exfat/dir.c   | 39 +++------------------------------------
>  fs/exfat/inode.c | 11 ++---------
>  2 files changed, 5 insertions(+), 45 deletions(-)
> 
> diff --git a/fs/exfat/dir.c b/fs/exfat/dir.c index
> 7619410d668e..cfc6f16a5fb2 100644
> --- a/fs/exfat/dir.c
> +++ b/fs/exfat/dir.c
> @@ -562,38 +562,6 @@ int exfat_put_dentry_set(struct 
> exfat_entry_set_cache *es, int sync)
>  	return err;
>  }
> 
> -static int exfat_walk_fat_chain(struct super_block *sb,
> -		struct exfat_chain *p_dir, unsigned int byte_offset,
> -		unsigned int *clu)
> -{
> -	struct exfat_sb_info *sbi = EXFAT_SB(sb);
> -	unsigned int clu_offset;
> -	unsigned int cur_clu;
> -
> -	clu_offset = EXFAT_B_TO_CLU(byte_offset, sbi);
> -	cur_clu = p_dir->dir;
> -
> -	if (p_dir->flags == ALLOC_NO_FAT_CHAIN) {
> -		cur_clu += clu_offset;
> -	} else {
> -		while (clu_offset > 0) {
> -			if (exfat_get_next_cluster(sb, &cur_clu))
> -				return -EIO;
> -			if (cur_clu == EXFAT_EOF_CLUSTER) {

The intentional exfat_fs_error() call for chain damage conditions is lost.
Instead of removing the error handling for this condition, it had better be
moved to exfat_find_location().

Other than this, the rest of the patchset looks excellent.
Thanks.

> -				exfat_fs_error(sb,
> -					"invalid dentry access beyond EOF
> (clu : %u, eidx : %d)",
> -					p_dir->dir,
> -					EXFAT_B_TO_DEN(byte_offset));
We lost 
> -				return -EIO;
> -			}
> -			clu_offset--;
> -		}
> -	}
> -
> -	*clu = cur_clu;
> -	return 0;
> -}
> -
>  static int exfat_find_location(struct super_block *sb, struct 
> exfat_chain *p_dir,
>  			       int entry, sector_t *sector, int *offset)  {
@@ -
> 603,7 +571,8 @@ static int exfat_find_location(struct super_block *sb, 
> struct exfat_chain *p_dir
> 
>  	off = EXFAT_DEN_TO_B(entry);
> 
> -	ret = exfat_walk_fat_chain(sb, p_dir, off, &clu);
> +	clu = p_dir->dir;
> +	ret = exfat_fat_walk(sb, &clu, EXFAT_B_TO_CLU(off, sbi), 
> +p_dir->flags);
>  	if (ret)
>  		return ret;
> 
> @@ -792,9 +761,7 @@ static int __exfat_get_dentry_set(struct 
> exfat_entry_set_cache *es,
>  		if (exfat_is_last_sector_in_cluster(sbi, sec)) {
>  			unsigned int clu = exfat_sector_to_cluster(sbi,
sec);
> 
> -			if (p_dir->flags == ALLOC_NO_FAT_CHAIN)
> -				clu++;
> -			else if (exfat_get_next_cluster(sb, &clu))
> +			if (exfat_fat_walk(sb, &clu, 1, p_dir->flags))
>  				goto put_es;
>  			sec = exfat_cluster_to_sector(sbi, clu);
>  		} else {
> diff --git a/fs/exfat/inode.c b/fs/exfat/inode.c index
> beb9ea7cca9f..817d9a135bb6 100644
> --- a/fs/exfat/inode.c
> +++ b/fs/exfat/inode.c
> @@ -225,15 +225,8 @@ static int exfat_map_cluster(struct inode *inode, 
> unsigned int clu_offset,
>  		 * *clu = (the first cluster of the allocated chain) =>
>  		 * (the last cluster of ...)
>  		 */
> -		if (ei->flags == ALLOC_NO_FAT_CHAIN) {
> -			*clu += num_to_be_allocated - 1;
> -		} else {
> -			while (num_to_be_allocated > 1) {
> -				if (exfat_get_next_cluster(sb, clu))
> -					return -EIO;
> -				num_to_be_allocated--;
> -			}
> -		}
> +		if (exfat_fat_walk(sb, clu, num_to_be_allocated - 1, ei-
> >flags))
> +			return -EIO;
>  		*count = 1;
>  	}
> 
> --
> 2.43.0



  reply	other threads:[~2026-04-02 14:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01  7:11 [PATCH v2 0/6] exfat: unify FAT chain walking helpers Chi Zhiling
2026-04-01  7:11 ` [PATCH v2 1/6] exfat: fix incorrect directory checksum after rename to shorter name Chi Zhiling
2026-04-01  7:11 ` [PATCH v2 2/6] exfat: introduce exfat_fat_walk helper Chi Zhiling
2026-04-03  2:34   ` Yuezhang.Mo
2026-04-03  2:44     ` Chi Zhiling
2026-04-01  7:11 ` [PATCH v2 3/6] exfat: use exfat_fat_walk helper to simplify fat entry walking Chi Zhiling
2026-04-02 14:22   ` Sungjong Seo [this message]
2026-04-03  2:43     ` Chi Zhiling
2026-04-01  7:11 ` [PATCH v2 4/6] exfat: remove NULL cache pointer case in exfat_ent_get Chi Zhiling
2026-04-01  7:11 ` [PATCH v2 5/6] exfat: introduce exfat_chain_advance helper Chi Zhiling
2026-04-03  2:34   ` Yuezhang.Mo
2026-04-03  2:47     ` Chi Zhiling
2026-04-03  3:33       ` Yuezhang.Mo
2026-04-03  4:28         ` Chi Zhiling
2026-04-01  7:11 ` [PATCH v2 6/6] exfat: use " Chi Zhiling

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='015c01dcc2ac$1ffd7520$5ff85f60$@samsung.com' \
    --to=sj1557.seo@samsung.com \
    --cc=chizhiling@163.com \
    --cc=chizhiling@kylinos.cn \
    --cc=cpgs@samsung.com \
    --cc=linkinjeon@kernel.org \
    --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