linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: fix wrong sum_page pointer in f2fs_gc
Date: Sun, 23 Oct 2016 20:26:15 +0800	[thread overview]
Message-ID: <3a96264b-b187-a5ce-2279-f9edd3748838@kernel.org> (raw)
In-Reply-To: <20161014165700.GA67182@jaegeuk>

On 2016/10/15 0:57, Jaegeuk Kim wrote:
> On Fri, Oct 14, 2016 at 09:25:59PM +0800, Chao Yu wrote:
>> On 2016/10/14 1:14, Jaegeuk Kim wrote:
>>> On Thu, Oct 13, 2016 at 06:33:19PM +0800, Chao Yu wrote:
>>>> 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?
>>>
>>> Well, it looks like no problem to remove this, since it will hit
>>> f2fs_cp_error(). I just intended to handle the above f2fs_bug_on here.
>>
>> If summary page becomes non-uptodate, it seems there is a bug in vfs/mm/f2fs,
>> why not keep it there to detect bug?
> 
> I found that the above get_sum_page() loop can give a page which is not uptodate
> caused by EIO. Then, we would get the above bug_on, if we move f2fs_cp_error()
> case like this patch.
> 
> Thoughts?

Seems this patch has already been merged into linus' tree...

Anyway, I can understand why you remove f2fs_bug_on & add PageUptodate here, but
why should we repositon below check?

if (get_valid_blocks(sbi, segno, 1) == 0 ||
		unlikely(f2fs_cp_error(sbi)))

Thanks,

> 
> Thanks,
> 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

  reply	other threads:[~2016-10-23 12:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 23:23 [PATCH] f2fs: fix wrong sum_page pointer in f2fs_gc Jaegeuk Kim
2016-10-13 10:33 ` Chao Yu
2016-10-13 17:14   ` Jaegeuk Kim
2016-10-14 13:25     ` Chao Yu
2016-10-14 16:57       ` Jaegeuk Kim
2016-10-23 12:26         ` Chao Yu [this message]
2016-10-23 21:40           ` Jaegeuk Kim
2016-10-24  2:55             ` 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=3a96264b-b187-a5ce-2279-f9edd3748838@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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).