From: Jan Kara <jack@suse.cz>
To: "zhangyi (F)" <yi.zhang@huawei.com>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca, miaoxie@huawei.com, jack@suse.cz
Subject: Re: [PATCH] ext4: fix incorrect quotaoff if the quota feature is enabled
Date: Tue, 22 Aug 2017 11:22:05 +0200 [thread overview]
Message-ID: <20170822092205.GA4909@quack2.suse.cz> (raw)
In-Reply-To: <1503384097-19206-1-git-send-email-yi.zhang@huawei.com>
On Tue 22-08-17 14:41:37, zhangyi (F) wrote:
> Current ext4 quota should always "usage enabled" if the
> quota feautre is enabled. But in ext4_orphan_cleanup(), it
> turn quota off directly (used for the older quota), so
> we cannot turn it on again via "quotaon" unless umount and
> remount ext4.
>
> Simple reproduce:
>
> mkfs.ext4 -O project,quota /dev/vdb1
> mount -o prjquota /dev/vdb1 /mnt
> chattr -p 123 /mnt
> chattr +P /mnt
> touch /mnt/aa /mnt/bb
> exec 100<>/mnt/aa
> rm -f /mnt/aa
> sync
> echo c > /proc/sysrq-trigger
>
> #reboot and mount
> mount -o prjquota /dev/vdb1 /mnt
> #query status
> quotaon -Ppv /dev/vdb1
> #output
> quotaon: Cannot find mountpoint for device /dev/vdb1
> quotaon: No correct mountpoint specified.
>
> This patch avoid incorrect quotaoff when ext4 has quota
> feautre. We also take care about the "quota on" part in
> ext4_orphan_cleanup(), it is used for journalled quota
> and not invoked if quota feature is enabled, so it's not
> affected.
>
> Signed-off-by: zhangyi (F) <yi.zhang@huawei.com>
> ---
> fs/ext4/super.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> index d61a70e2..c1b23b1 100644
> --- a/fs/ext4/super.c
> +++ b/fs/ext4/super.c
> @@ -2510,10 +2510,12 @@ static void ext4_orphan_cleanup(struct super_block *sb,
> ext4_msg(sb, KERN_INFO, "%d truncate%s cleaned up",
> PLURAL(nr_truncates));
> #ifdef CONFIG_QUOTA
> - /* Turn quotas off */
> - for (i = 0; i < EXT4_MAXQUOTAS; i++) {
> - if (sb_dqopt(sb)->files[i])
> - dquot_quota_off(sb, i);
> + if (!ext4_has_feature_quota(sb)) {
> + /* Turn quotas off */
> + for (i = 0; i < EXT4_MAXQUOTAS; i++) {
> + if (sb_dqopt(sb)->files[i])
> + dquot_quota_off(sb, i);
> + }
So this should work however I'd prefer if we kept the test symmetric to the
place where we turn quotas on for orphan cleanup. I.e. something like:
for (i = 0; i < EXT4_MAXQUOTAS; i++) {
/* Old style journalled quotas enabled for orphan cleanup? */
if (EXT4_SB(sb)->s_qf_names[i] && sb_dqopt(sb)->files[i])
dquot_quota_off(sb, i);
}
Also when looking at this code I've noticed that quota does not get enabled
if we use quota feature and we do orphan replay on read-only filesystem.
Could you fix that by handling this case in ext4_orphan_cleanup() as well?
Thanks!
Honza
> }
> #endif
> sb->s_flags = s_flags; /* Restore MS_RDONLY status */
> --
> 2.5.0
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-08-22 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 6:41 [PATCH] ext4: fix incorrect quotaoff if the quota feature is enabled zhangyi (F)
2017-08-22 9:22 ` Jan Kara [this message]
2017-08-22 9:38 ` zhangyi (F)
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=20170822092205.GA4909@quack2.suse.cz \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=tytso@mit.edu \
--cc=yi.zhang@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;
as well as URLs for NNTP newsgroup(s).