From: Jan Kara <jack@suse.cz>
To: Chao Yu <yuchao0@huawei.com>
Cc: Jan Kara <jack@suse.com>,
chao@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] quota: fix wrong condition in is_quota_modification()
Date: Thu, 12 Sep 2019 12:06:10 +0200 [thread overview]
Message-ID: <20190912100610.GA14773@quack2.suse.cz> (raw)
In-Reply-To: <20190911093650.35329-1-yuchao0@huawei.com>
On Wed 11-09-19 17:36:50, Chao Yu wrote:
> Quoted from
> commit 3da40c7b0898 ("ext4: only call ext4_truncate when size <= isize")
>
> " At LSF we decided that if we truncate up from isize we shouldn't trim
> fallocated blocks that were fallocated with KEEP_SIZE and are past the
> new i_size. This patch fixes ext4 to do this. "
>
> And generic/092 of fstest have covered this case for long time, however
> is_quota_modification() didn't adjust based on that rule, so that in
> below condition, we will lose to quota block change:
> - fallocate blocks beyond EOF
> - remount
> - truncate(file_path, file_size)
>
> Fix it.
>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
> include/linux/quotaops.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/quotaops.h b/include/linux/quotaops.h
> index dc905a4ff8d7..bd30acad3a7f 100644
> --- a/include/linux/quotaops.h
> +++ b/include/linux/quotaops.h
> @@ -22,7 +22,7 @@ static inline struct quota_info *sb_dqopt(struct super_block *sb)
> /* i_mutex must being held */
> static inline bool is_quota_modification(struct inode *inode, struct iattr *ia)
> {
> - return (ia->ia_valid & ATTR_SIZE && ia->ia_size != inode->i_size) ||
> + return (ia->ia_valid & ATTR_SIZE && ia->ia_size <= inode->i_size) ||
> (ia->ia_valid & ATTR_UID && !uid_eq(ia->ia_uid, inode->i_uid)) ||
> (ia->ia_valid & ATTR_GID && !gid_eq(ia->ia_gid, inode->i_gid));
> }
OK, but your change makes i_size extension not to be quota modification
which is IMO wrong. So I think the condition should just be:
return (ia->ia_valid & ATTR_SIZE) || ...
I'll fix the patch up and pull it into my tree.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2019-09-12 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 9:36 Chao Yu
2019-09-12 10:06 ` Jan Kara [this message]
2019-09-16 2:53 ` Chao Yu
2019-09-16 8:23 ` Jan Kara
2019-09-17 1:44 ` Chao Yu
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=20190912100610.GA14773@quack2.suse.cz \
--to=jack@suse.cz \
--cc=chao@kernel.org \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.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
all inboxes | Powered by JetHome®