All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Sheng Yong <shengyong1@huawei.com>,
	jaegeuk@kernel.org, yuchao0@huawei.com
Cc: miaoxie@huawei.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/3] f2fs: quota: decrease the lock granularity of statfs_project
Date: Wed, 25 Jul 2018 23:41:39 +0800	[thread overview]
Message-ID: <58d96b9e-3714-5838-d577-81d1c43bfe72@kernel.org> (raw)
In-Reply-To: <20180724121754.19920-2-shengyong1@huawei.com>

On 2018/7/24 20:17, Sheng Yong wrote:
> According to fs/quota/dquot.c, `dq_data_lock' protects mem_dqinfo
> structures and modifications of dquot pointers in the inode, and
> `dquot->dq_dqb_lock' protects data from dq_dqb.
> 
> We should use dquot->dq_dqb_lock in statfs_project instead of
> dq_dat_lock.
> 
> Signed-off-by: Sheng Yong <shengyong1@huawei.com>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

  reply	other threads:[~2018-07-25 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 12:17 [PATCH 1/3] f2fs: quota: do not mount as RDWR without QUOTA if quota feature enabled Sheng Yong
2018-07-24 12:17 ` [PATCH 2/3] f2fs: quota: decrease the lock granularity of statfs_project Sheng Yong
2018-07-25 15:41   ` Chao Yu [this message]
2018-07-24 12:17 ` [PATCH 3/3] f2fs: quota: fix incorrect error message and comments Sheng Yong
2018-07-25 15:44   ` Chao Yu
2018-07-26  1:58     ` Sheng Yong
2018-07-26 11:24   ` [PATCH v2] f2fs: quota: fix incorrect comments Sheng Yong
2018-07-26 11:33     ` Chao Yu
2018-07-25 15:27 ` [PATCH 1/3] f2fs: quota: do not mount as RDWR without QUOTA if quota feature enabled 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=58d96b9e-3714-5838-d577-81d1c43bfe72@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=miaoxie@huawei.com \
    --cc=shengyong1@huawei.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.