From: Chao Yu <chao2.yu@samsung.com>
To: 'Jaegeuk Kim' <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: do not trim preallocated blocks when truncating after i_size
Date: Tue, 09 Jun 2015 10:22:49 +0800 [thread overview]
Message-ID: <007a01d0a25b$4dbb2b60$e9318220$@samsung.com> (raw)
In-Reply-To: <20150608180643.GA59258@jaegeuk-mac02.mot.com>
> -----Original Message-----
> From: Jaegeuk Kim [mailto:jaegeuk@kernel.org]
> Sent: Tuesday, June 09, 2015 2:07 AM
> To: Chao Yu
> Cc: linux-f2fs-devel@lists.sourceforge.net; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] f2fs: do not trim preallocated blocks when truncating after i_size
>
> On Fri, Jun 05, 2015 at 06:34:02PM +0800, Chao Yu wrote:
> > When we perform generic/092 in xfstests, output is like below:
> >
> > XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > 0: [0..10239]: data
> > 0: [0..10239]: data
> > -1: [10240..20479]: unwritten
> > +1: [10240..14335]: unwritten
> >
> > This is because with this testcase, we redefine the regulation for
> > truncate in perallocated space past i_size as below:
> >
> > "There was some confused about what the fs was supposed to do when you
> > truncate at i_size with preallocated space past i_size. We decided on the
> > following things.
> >
> > 1) truncate(i_size) will trim all blocks past i_size.
> > 2) truncate(x) where x > i_size will not trim all blocks past i_size.
> > "
> >
> > This method is used in xfs, and then ext4/btrfs will follow the rule.
> >
> > This patch fixes to follow the new rule for f2fs.
> >
> > Signed-off-by: Chao Yu <chao2.yu@samsung.com>
> > ---
> > fs/f2fs/file.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> > index 4d42d66..85f97af 100644
> > --- a/fs/f2fs/file.c
> > +++ b/fs/f2fs/file.c
> > @@ -651,16 +651,16 @@ int f2fs_setattr(struct dentry *dentry, struct iattr *attr)
> > f2fs_get_encryption_info(inode))
> > return -EACCES;
> >
> > - if (attr->ia_size != i_size_read(inode)) {
> > + if (attr->ia_size <= i_size_read(inode)) {
> > truncate_setsize(inode, attr->ia_size);
> > f2fs_truncate(inode);
> > f2fs_balance_fs(F2FS_I_SB(inode));
> > } else {
> > /*
> > - * giving a chance to truncate blocks past EOF which
> > - * are fallocated with FALLOC_FL_KEEP_SIZE.
> > + * do not trim all blocks after i_size if target size is
> > + * larger than i_size.
> > */
> > - f2fs_truncate(inode);
> > + truncate_setsize(inode, attr->ia_size);
>
> So, we can do:
> truncate_setsize();
>
> if (attr->ia_size <= i_size_read(inode)) {
> f2fs_truncate(inode);
> f2fs_balance_fs();
> }
>
> Right?
Yes, let me fix and resend the patch.
Thanks,
>
> > }
> > }
> >
> > --
> > 2.4.2
------------------------------------------------------------------------------
prev parent reply other threads:[~2015-06-09 2:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 10:34 [PATCH] f2fs: do not trim preallocated blocks when truncating after i_size Chao Yu
2015-06-08 18:06 ` Jaegeuk Kim
2015-06-09 2:22 ` Chao Yu [this message]
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='007a01d0a25b$4dbb2b60$e9318220$@samsung.com' \
--to=chao2.yu@samsung.com \
--cc=jaegeuk@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).