linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v2] f2fs: add a rw_sem to cover quota flag changes
Date: Tue, 4 Jun 2019 17:48:52 +0800	[thread overview]
Message-ID: <c4348b1c-02ba-44e7-598c-e2435e53077d@huawei.com> (raw)
In-Reply-To: <20190530175714.GB28719@jaegeuk-macbookpro.roam.corp.google.com>

On 2019/5/31 1:57, Jaegeuk Kim wrote:
> thread 1:                        thread 2:
> writeback                        checkpoint
> set QUOTA_NEED_FLUSH
>                                  clear QUOTA_NEED_FLUSH
> f2fs_dquot_commit
> dquot_commit
> clear_dquot_dirty
>                                  f2fs_quota_sync
>                                  dquot_writeback_dquots
> 				 nothing to commit
> commit_dqblk
> quota_write
> f2fs_quota_write
> waiting for f2fs_lock_op()
> 				 pass __need_flush_quota
>                                  (no F2FS_DIRTY_QDATA)
> 
> -> up-to-date quota is not written
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

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

Thanks,

  reply	other threads:[~2019-06-04  9:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  3:31 [PATCH] f2fs: add a rw_sem to cover quota flag changes Jaegeuk Kim
2019-05-30 14:01 ` [f2fs-dev] " Chao Yu
2019-05-30 17:57 ` [PATCH v2] " Jaegeuk Kim
2019-06-04  9:48   ` Chao Yu [this message]
2019-06-04 18:36   ` [f2fs-dev] [PATCH v3] " Jaegeuk Kim
2019-06-11  7:46     ` Chao Yu
2019-06-11  7:46       ` Chao Yu
2019-06-14  2:46       ` Jaegeuk Kim
2019-06-14  2:46         ` [f2fs-dev] " Jaegeuk Kim
2019-06-18  6:52         ` Chao Yu
2019-06-19 17:26           ` Jaegeuk Kim
2019-06-20  2:03             ` Chao Yu
2019-06-21 17:38               ` Jaegeuk Kim
2019-06-21 17:51                 ` Jaegeuk Kim
2019-06-24  1:06                   ` 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=c4348b1c-02ba-44e7-598c-e2435e53077d@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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).