mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-fsdevel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [PATCH] f2fs: fix wrong sum_page pointer in f2fs_gc
Date: Thu, 13 Oct 2016 18:33:19 +0800	[thread overview]
Message-ID: <faeadd54-7814-41b5-b041-2d0eb819c3f6@huawei.com> (raw)
In-Reply-To: <20161012232304.6667-1-jaegeuk@kernel.org>

Hi Jaegeuk,

On 2016/10/13 7:23, Jaegeuk Kim wrote:
> This patch fixes using a wrong pointer for sum_page in f2fs_gc.
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
>  fs/f2fs/gc.c | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> index e48142f..9c18917 100644
> --- a/fs/f2fs/gc.c
> +++ b/fs/f2fs/gc.c
> @@ -854,16 +854,16 @@ static int do_garbage_collect(struct f2fs_sb_info *sbi,
>  
>  	for (segno = start_segno; segno < end_segno; segno++) {
>  
> -		if (get_valid_blocks(sbi, segno, 1) == 0 ||
> -					unlikely(f2fs_cp_error(sbi)))
> -			goto next;
> -
>  		/* find segment summary of victim */
>  		sum_page = find_get_page(META_MAPPING(sbi),
>  					GET_SUM_BLOCK(sbi, segno));
> -		f2fs_bug_on(sbi, !PageUptodate(sum_page));
>  		f2fs_put_page(sum_page, 0);
>  
> +		if (get_valid_blocks(sbi, segno, 1) == 0 ||
> +				!PageUptodate(sum_page) ||

Why uptodate flag of summary page can be cleared? someone truncates it?

Thanks,

> +				unlikely(f2fs_cp_error(sbi)))
> +			goto next;
> +
>  		sum = page_address(sum_page);
>  		f2fs_bug_on(sbi, type != GET_SUM_TYPE((&sum->footer)));
>  
> 

  reply	other threads:[~2016-10-13 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 23:23 Jaegeuk Kim
2016-10-13 10:33 ` Chao Yu [this message]
2016-10-13 17:14   ` 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=faeadd54-7814-41b5-b041-2d0eb819c3f6@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=jaegeuk@kernel.org \
    --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

all inboxes | Powered by JetHome®