From: Jan Kara <jack@suse.cz>
To: yangerkun <yangerkun@huawei.com>
Cc: jack@suse.com, yi.zhang@huawei.com, houtao1@huawei.com,
miaoxie@huawei.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] quota: fix a problem about transfer quota
Date: Tue, 26 Mar 2019 17:43:36 +0100 [thread overview]
Message-ID: <20190326164336.GA6294@quack2.suse.cz> (raw)
In-Reply-To: <1553608802-80648-1-git-send-email-yangerkun@huawei.com>
On Tue 26-03-19 22:00:02, yangerkun wrote:
> Run below script as root, dquot_add_space will return -EDQUOT since
> __dquot_transfer call dquot_add_space with flags=0, and dquot_add_space
> think it's a preallocation. Fix it by set flags as DQUOT_SPACE_WARN.
>
> mkfs.ext4 -O quota,project /dev/vdb
> mount -o prjquota /dev/vdb /mnt
> setquota -P 23 1 1 0 0 /dev/vdb
> dd if=/dev/zero of=/mnt/test-file bs=4K count=1
> chattr -p 23 test-file
>
> Fixes: 7b9ca4c61("quota: Reduce contention on dq_data_lock")
> Signed-off-by: yangerkun <yangerkun@huawei.com>
Thanks! I've added the fix to my tree.
Honza
> ---
> fs/quota/dquot.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/quota/dquot.c b/fs/quota/dquot.c
> index fc20e06..dd1783e 100644
> --- a/fs/quota/dquot.c
> +++ b/fs/quota/dquot.c
> @@ -1993,8 +1993,8 @@ int __dquot_transfer(struct inode *inode, struct dquot **transfer_to)
> &warn_to[cnt]);
> if (ret)
> goto over_quota;
> - ret = dquot_add_space(transfer_to[cnt], cur_space, rsv_space, 0,
> - &warn_to[cnt]);
> + ret = dquot_add_space(transfer_to[cnt], cur_space, rsv_space,
> + DQUOT_SPACE_WARN, &warn_to[cnt]);
> if (ret) {
> spin_lock(&transfer_to[cnt]->dq_dqb_lock);
> dquot_decr_inodes(transfer_to[cnt], inode_usage);
> --
> 2.7.4
>
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2019-03-26 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 14:00 [PATCH v2] quota: fix a problem about transfer quota yangerkun
2019-03-26 16:43 ` Jan Kara [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=20190326164336.GA6294@quack2.suse.cz \
--to=jack@suse.cz \
--cc=houtao1@huawei.com \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=yangerkun@huawei.com \
--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).