From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Chao Yu <yuchao0@huawei.com>
Subject: Re: [PATCH 1/2] f2fs: fix to commit bio cache after flushing node pages
Date: Mon, 26 Sep 2016 11:33:21 -0700 [thread overview]
Message-ID: <20160926183321.GB33149@jaegeuk> (raw)
In-Reply-To: <1474906193-6487-1-git-send-email-chao@kernel.org>
Hi Chao,
On Tue, Sep 27, 2016 at 12:09:52AM +0800, Chao Yu wrote:
> From: Chao Yu <yuchao0@huawei.com>
>
> In sync_node_pages, we won't check and commit last merged pages in private
> bio cache of f2fs, as these pages were taged as writeback, someone who is
> waiting for writebacking of the page will be blocked until the cache was
> committed by someone else.
>
> We need to commit node type bio cache to avoid potential deadlock or long
> delay of waiting writeback.
>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
> fs/f2fs/node.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
> index 9faddcd..f73f774 100644
> --- a/fs/f2fs/node.c
> +++ b/fs/f2fs/node.c
> @@ -1416,6 +1416,7 @@ int sync_node_pages(struct f2fs_sb_info *sbi, struct writeback_control *wbc)
> struct pagevec pvec;
> int step = 0;
> int nwritten = 0;
> + int ret = 0;
>
> pagevec_init(&pvec, 0);
>
> @@ -1436,7 +1437,8 @@ next_step:
>
> if (unlikely(f2fs_cp_error(sbi))) {
> pagevec_release(&pvec);
> - return -EIO;
> + ret = -EIO;
> + goto out;
> }
>
> /*
> @@ -1487,6 +1489,8 @@ continue_unlock:
>
> if (NODE_MAPPING(sbi)->a_ops->writepage(page, wbc))
> unlock_page(page);
> + else
> + nwritten++;
>
> if (--wbc->nr_to_write == 0)
> break;
> @@ -1504,7 +1508,10 @@ continue_unlock:
> step++;
> goto next_step;
> }
> - return nwritten;
> +out:
> + if (nwritten)
> + f2fs_submit_merged_bio(sbi, NODE, WRITE);
IIRC, we don't need to flush this, since f2fs_submit_merged_bio_cond() would
handle this in f2fs_wait_on_page_writeback().
Thanks,
> + return ret;
> }
>
> int wait_on_node_pages_writeback(struct f2fs_sb_info *sbi, nid_t ino)
> --
> 2.7.2
next prev parent reply other threads:[~2016-09-26 18:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 16:09 Chao Yu
2016-09-26 16:09 ` [PATCH 2/2] f2fs: remove redundant io plug Chao Yu
2016-09-26 18:33 ` Jaegeuk Kim [this message]
2016-09-27 0:57 ` [PATCH 1/2] f2fs: fix to commit bio cache after flushing node pages Chao Yu
2016-09-27 1:39 ` Jaegeuk Kim
2016-09-27 2:09 ` Chao Yu
2016-09-28 20:19 ` Jaegeuk Kim
2016-09-29 10:45 ` Chao Yu
2016-09-29 23:45 ` Jaegeuk Kim
2016-09-29 10:50 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=20160926183321.GB33149@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®