From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: chao@kernel.org, Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: support zero sized file truncate for device aliasing files
Date: Tue, 18 Mar 2025 11:45:30 +0800 [thread overview]
Message-ID: <ea3988c6-7708-4da9-8009-85708a27275b@kernel.org> (raw)
In-Reply-To: <20250317190809.678626-1-daeho43@gmail.com>
On 3/18/25 03:08, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> support a file truncation to zero size for device aliasing files.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> ---
> fs/f2fs/file.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index f92a9fba9991..7ae5a5af5ed9 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -1036,7 +1036,7 @@ int f2fs_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
>
> if ((attr->ia_valid & ATTR_SIZE)) {
> if (!f2fs_is_compress_backend_ready(inode) ||
> - IS_DEVICE_ALIASING(inode))
> + (IS_DEVICE_ALIASING(inode) && attr->ia_size))
> return -EOPNOTSUPP;
> if (is_inode_flag_set(inode, FI_COMPRESS_RELEASED) &&
> !IS_ALIGNED(attr->ia_size,
> @@ -1117,6 +1117,9 @@ int f2fs_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
> if (err)
> return err;
Daeho,
If truncate(, 0) failed due to some reasons, maybe, the file was partially
truncated, should we tag it as inconsistent status to avoid its later access?
thoughts?
Thanks,
>
> + if (IS_DEVICE_ALIASING(inode))
> + f2fs_destroy_extent_tree(inode);
> +
> spin_lock(&fi->i_size_lock);
> inode_set_mtime_to_ts(inode, inode_set_ctime_current(inode));
> fi->last_disk_size = i_size_read(inode);
next prev parent reply other threads:[~2025-03-18 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 19:08 [PATCH] f2fs: support zero sized file truncate for device aliasing files Daeho Jeong
2025-03-18 3:45 ` Chao Yu [this message]
2025-03-21 21:16 ` [f2fs-dev] " Daeho Jeong
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=ea3988c6-7708-4da9-8009-85708a27275b@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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