From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: avoid infinite GC loop due to stale atomic files
Date: Mon, 16 Sep 2019 09:15:35 +0800 [thread overview]
Message-ID: <1ba048b4-7dac-1c98-837d-0f0456ccc560@huawei.com> (raw)
In-Reply-To: <20190910120913.GB98080@jaegeuk-macbookpro.roam.corp.google.com>
On 2019/9/10 20:09, Jaegeuk Kim wrote:
>> The lock is used to protect F2FS_I(inode)->inmem_pages list... it should be kept?
> Urg.. yup. I added.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-09-16 1:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 1:25 [f2fs-dev] [PATCH 1/2] f2fs: do not select same victim right again Jaegeuk Kim
2019-09-09 1:25 ` [f2fs-dev] [PATCH 2/2] f2fs: avoid infinite GC loop due to stale atomic files Jaegeuk Kim
2019-09-09 3:03 ` Chao Yu
2019-09-09 7:30 ` Jaegeuk Kim
2019-09-09 7:54 ` Chao Yu
2019-09-09 8:01 ` Jaegeuk Kim
2019-09-09 8:05 ` Chao Yu
2019-09-09 8:21 ` Jaegeuk Kim
2019-09-09 8:27 ` Chao Yu
2019-09-09 8:38 ` Jaegeuk Kim
2019-09-09 8:44 ` Jaegeuk Kim
2019-09-09 11:26 ` Chao Yu
2019-09-09 14:34 ` Jaegeuk Kim
2019-09-10 0:59 ` Chao Yu
2019-09-10 11:58 ` Jaegeuk Kim
2019-09-10 12:04 ` Chao Yu
2019-09-10 12:09 ` Jaegeuk Kim
2019-09-16 1:15 ` Chao Yu [this message]
2019-09-09 2:56 ` [f2fs-dev] [PATCH 1/2] f2fs: do not select same victim right again Chao Yu
2019-09-09 8:06 ` Jaegeuk Kim
2019-09-09 11:32 ` Chao Yu
2019-09-09 12:04 ` Jaegeuk Kim
2019-09-16 1:22 ` Chao Yu
2019-09-16 15:37 ` Jaegeuk Kim
2019-09-17 1:42 ` Chao Yu
2019-09-17 20:55 ` Jaegeuk Kim
2019-09-18 1:43 ` Chao Yu
2019-09-18 3:12 ` Jaegeuk Kim
2019-09-18 3:26 ` Chao Yu
2019-09-18 16:47 ` Jaegeuk Kim
2019-09-19 0:53 ` Chao Yu
2019-09-19 17:11 ` Jaegeuk Kim
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=1ba048b4-7dac-1c98-837d-0f0456ccc560@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).