From: Jan Kara <jack@suse.cz>
To: Chao Yu <yuchao0@huawei.com>
Cc: Jan Kara <jack@suse.cz>, 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: Mon, 16 Sep 2019 10:23:06 +0200 [thread overview]
Message-ID: <20190916082306.GB2485@quack2.suse.cz> (raw)
In-Reply-To: <ce4fe030-7ad4-134d-e0c4-77dc2c618b15@huawei.com>
On Mon 16-09-19 10:53:08, Chao Yu wrote:
> On 2019/9/12 18:06, Jan Kara wrote:
> > On Wed 11-09-19 17:36:50, Chao Yu wrote:
> >> 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
>
> I just try to adapt below rules covered with generic/092, which restrict
> to not trim preallocate blocks beyond i_size, in that case, filesystem
> won't change i_blocks.
>
> 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.
Ah, OK.
> However, I'm okay with your change, because there could be filesystems won't
> follow above rule.
Yes, I'm concerned that some filesystem may change i_blocks in some corner
case when growing inode size (e.g. when it decides to convert inode from
inline format to a normal block based format or something like that). So I
don't think the optimization is really worth the chance for breakage.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2019-09-16 8:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 9:36 [PATCH] quota: fix wrong condition in is_quota_modification() Chao Yu
2019-09-12 10:06 ` Jan Kara
2019-09-16 2:53 ` Chao Yu
2019-09-16 8:23 ` Jan Kara [this message]
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=20190916082306.GB2485@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