From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>
Cc: zhangdianfang@huawei.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH v5] f2fs: introduce a method to make nat journal more fresh
Date: Sat, 14 Apr 2018 09:22:35 +0800 [thread overview]
Message-ID: <dd356978-c426-4b7c-2494-f7fd02d2ccb2@kernel.org> (raw)
In-Reply-To: <20180414004800.GA35840@jaegeuk-macbookpro.roam.corp.google.com>
On 2018/4/14 8:48, Jaegeuk Kim wrote:
> I removed this patch in my test branch, since it simply gave a kernel panic.
> Please test before sending patches.
Sorry, I didn't find this bug in previous review.
Look at this patch again,
> + /* journal hit case, try to locate set in journal */
> + if (!remove_journal && head->entry_cnt <= NAT_JOURNAL_ENTRIES)
head pointer can be a random value before using.
To Yunlei, could you please fix this, and do the test (at least with xfstest)
before resending it.
Thanks,
>
> repro
> 1. encrypt a dir
> 2. dd to create 10MB-sized file in the dir
>
> On 04/12, Chao Yu wrote:
>> On 2018/4/10 15:11, Yunlei He wrote:
>>> This patch introduce a method to make nat journal more fresh:
>>> i. sort set list using dirty entry number and cp version
>>> average value.
>>> ii. if meet with cache hit, update average version valus with
>>> current cp version.
>>>
>>> With this patch, newly modified nat set will flush to journal,
>>> and flush old nat set with same dirty entry number to nat area.
>>>
>>> Signed-off-by: Yunlei He <heyunlei@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
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
prev parent reply other threads:[~2018-04-14 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 7:11 [PATCH v5] f2fs: introduce a method to make nat journal more fresh Yunlei He
2018-04-12 9:42 ` Chao Yu
2018-04-14 0:48 ` Jaegeuk Kim
2018-04-14 1:22 ` Chao Yu [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=dd356978-c426-4b7c-2494-f7fd02d2ccb2@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.com \
--cc=zhangdianfang@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).