From: Jaegeuk Kim <jaegeuk@kernel.org>
To: He YunLei <heyunlei@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Bintian <bintian.wang@huawei.com>
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: check only data or node for summary
Date: Wed, 6 Jul 2016 10:50:05 -0700 [thread overview]
Message-ID: <20160706175005.GA80939@jaegeuk> (raw)
In-Reply-To: <577C8468.3060503@huawei.com>
On Wed, Jul 06, 2016 at 12:09:12PM +0800, He YunLei wrote:
> On 2016/6/11 5:01, Jaegeuk Kim wrote:
> > We can check data or node types only for gc, since we allocate different type of
> > data/node blocks in a different logs occasionally.
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> > ---
> > fs/f2fs/gc.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> > index e1d274c..c2c4ac3 100644
> > --- a/fs/f2fs/gc.c
> > +++ b/fs/f2fs/gc.c
> > @@ -806,7 +806,8 @@ static int do_garbage_collect(struct f2fs_sb_info *sbi,
> > f2fs_put_page(sum_page, 0);
> >
> > sum = page_address(sum_page);
> > - f2fs_bug_on(sbi, type != GET_SUM_TYPE((&sum->footer)));
> > + f2fs_bug_on(sbi, IS_DATASEG(type) !=
> > + IS_DATASEG(GET_SUM_TYPE((&sum->footer))));
>
> Hi, Kim
> type has been transformed into SUM_TYPE_DATA or SUM_TYPE_NODE, so here
> no need to do this.
Oops, right. :)
Thanks,
prev parent reply other threads:[~2016-07-06 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 21:01 [PATCH 1/2] f2fs: check only data or node for summary Jaegeuk Kim
2016-06-10 21:01 ` [PATCH 2/2] f2fs: report error for f2fs_parent_dir Jaegeuk Kim
2016-07-06 4:09 ` [f2fs-dev] [PATCH 1/2] f2fs: check only data or node for summary He YunLei
2016-07-06 17:50 ` Jaegeuk Kim [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=20160706175005.GA80939@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=bintian.wang@huawei.com \
--cc=heyunlei@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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