The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Namjae Jeon <linkinjeon@kernel.org>
To: sj1557.seo@samsung.com, yuezhang.mo@sony.com, brauner@kernel.org,
	djwong@kernel.org, hch@lst.de
Cc: linux-fsdevel@vger.kernel.org, anmuxixixi@gmail.com,
	dxdt@dev.snart.me, chizhiling@kylinos.cn, chizhiling@163.com,
	linux-kernel@vger.kernel.org, charsyam@gmail.com,
	Namjae Jeon <linkinjeon@kernel.org>
Subject: [PATCH v4 11/11] exfat: make exfat_truncate() return error code
Date: Mon, 18 May 2026 20:47:05 +0900	[thread overview]
Message-ID: <20260518114705.9601-12-linkinjeon@kernel.org> (raw)
In-Reply-To: <20260518114705.9601-1-linkinjeon@kernel.org>

Convert exfat_truncate() to return int, and make it return the error
code on failure. Update exfat_setattr() to handle the returned error
appropriately.

Acked-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
---
 fs/exfat/file.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/fs/exfat/file.c b/fs/exfat/file.c
index d9c4e8dd9fd8..1271202b35ed 100644
--- a/fs/exfat/file.c
+++ b/fs/exfat/file.c
@@ -292,7 +292,7 @@ int __exfat_truncate(struct inode *inode)
 	return 0;
 }
 
-static void exfat_truncate(struct inode *inode)
+static int exfat_truncate(struct inode *inode)
 {
 	struct super_block *sb = inode->i_sb;
 	struct exfat_sb_info *sbi = EXFAT_SB(sb);
@@ -315,6 +315,8 @@ static void exfat_truncate(struct inode *inode)
 	inode->i_blocks = round_up(i_size_read(inode), sbi->cluster_size) >> 9;
 write_size:
 	mutex_unlock(&sbi->s_lock);
+
+	return err;
 }
 
 int exfat_getattr(struct mnt_idmap *idmap, const struct path *path,
@@ -400,7 +402,7 @@ int exfat_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
 		 * __exfat_write_inode() is called from exfat_truncate(), inode
 		 * is already written by it, so mark_inode_dirty() is unneeded.
 		 */
-		exfat_truncate(inode);
+		error = exfat_truncate(inode);
 		up_write(&EXFAT_I(inode)->truncate_lock);
 	} else
 		mark_inode_dirty(inode);
-- 
2.25.1


  parent reply	other threads:[~2026-05-18 11:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 11:46 [PATCH v4 00/11] exfat: convert to iomap Namjae Jeon
2026-05-18 11:46 ` [PATCH v4 01/11] iomap: introduce IOMAP_F_ZERO_TAIL flag Namjae Jeon
2026-05-18 16:03   ` Darrick J. Wong
2026-05-19  3:32     ` Namjae Jeon
2026-05-22 12:53   ` Christian Brauner
2026-05-22 15:02     ` Namjae Jeon
2026-05-18 11:46 ` [PATCH v4 02/11] exfat: replace unsafe macros with static inline functions Namjae Jeon
2026-05-18 11:46 ` [PATCH v4 03/11] exfat: add balloc parameter to exfat_map_cluster() for iomap support Namjae Jeon
2026-05-18 11:46 ` [PATCH v4 04/11] exfat: add exfat_file_open() Namjae Jeon
2026-05-18 11:46 ` [PATCH v4 05/11] exfat: add support for multi-cluster allocation Namjae Jeon
2026-05-18 11:47 ` [PATCH v4 06/11] exfat: add data_start_bytes and exfat_cluster_to_phys_bytes() helper Namjae Jeon
2026-05-18 11:47 ` [PATCH v4 07/11] exfat: fix implicit declaration of brelse() Namjae Jeon
2026-05-18 11:47 ` [PATCH v4 08/11] exfat: add iomap buffered I/O support Namjae Jeon
2026-05-19  5:21   ` Yuezhang.Mo
2026-05-18 11:47 ` [PATCH v4 09/11] exfat: add iomap direct " Namjae Jeon
2026-05-18 11:47 ` [PATCH v4 10/11] exfat: add support for SEEK_HOLE and SEEK_DATA in llseek Namjae Jeon
2026-05-18 11:47 ` Namjae Jeon [this message]
2026-05-19  3:40 ` [PATCH v4 00/11] exfat: convert to iomap Darrick J. Wong
2026-05-19  4:05   ` Namjae Jeon
2026-05-19  7:04 ` Christoph Hellwig
2026-05-19  7:45   ` Namjae Jeon
2026-05-22 12:53 ` (subset) " Christian Brauner

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=20260518114705.9601-12-linkinjeon@kernel.org \
    --to=linkinjeon@kernel.org \
    --cc=anmuxixixi@gmail.com \
    --cc=brauner@kernel.org \
    --cc=charsyam@gmail.com \
    --cc=chizhiling@163.com \
    --cc=chizhiling@kylinos.cn \
    --cc=djwong@kernel.org \
    --cc=dxdt@dev.snart.me \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.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