All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sheng Yong <shengyong1@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [RFC PATCH v2 2/2] f2fs: do not set LOST_PINO for renamed dir
Date: Sun, 2 Jul 2017 12:09:09 +0800	[thread overview]
Message-ID: <c6de6bcd-2ca8-1a3b-71b7-be99ed832fb4@huawei.com> (raw)
In-Reply-To: <20170701151039.GD901@jaegeuk-macbookpro.roam.corp.google.com>

Hi, Jaegeuk

On 2017/7/1 23:10, Jaegeuk Kim wrote:
> Hi,
> 
> On 06/26, Sheng Yong wrote:
>> After renaming a directory, fsck could detect unmatched pino. The scenario
>> can be reproduced as the following:
>>
>> 	$ mkdir /bar/subbar /foo
>> 	$ rename /bar/subbar /foo
>>
>> Then fsck will report:
>> [ASSERT] (__chk_dots_dentries:1182)  --> Bad inode number[0x3] for '..', parent parent ino is [0x4]
> 
> Does fsck report this? If LOST_PINO is found, it must skip parent ino?
Yes, fsck should skip checking pino if LOST_PINO is set. Meanwhile, I think
we don't have to set LOST_PINO when rename a dir, since dir is not involved
in recover and its pino will never get fixed.

thanks,
Sheng
> 
>>
>> Rename sets LOST_PINO for old_inode. However, the flag cannot be cleared,
>> since dir is written back with CP. So, let's get rid of LOST_PINO for a
>> renamed dir and fix the pino directly at the end of rename.
>>
>> Signed-off-by: Sheng Yong <shengyong1@huawei.com>
>> ---
>>   fs/f2fs/namei.c | 5 ++++-
>>   1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/f2fs/namei.c b/fs/f2fs/namei.c
>> index c31b40e5f9cf..b75dc2f4ad57 100644
>> --- a/fs/f2fs/namei.c
>> +++ b/fs/f2fs/namei.c
>> @@ -772,7 +772,10 @@ static int f2fs_rename(struct inode *old_dir, struct dentry *old_dentry,
>>   	}
>>   
>>   	down_write(&F2FS_I(old_inode)->i_sem);
>> -	file_lost_pino(old_inode);
>> +	if (!old_dir_entry || whiteout)
>> +		file_lost_pino(old_inode);
>> +	else
>> +		F2FS_I(old_inode)->i_pino = new_dir->i_ino;
>>   	up_write(&F2FS_I(old_inode)->i_sem);
>>   
>>   	old_inode->i_ctime = current_time(old_inode);
>> -- 
>> 2.11.0
>>
>>
>> ------------------------------------------------------------------------------
>> 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

  reply	other threads:[~2017-07-02  4:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26  2:41 [RFC PATCH v2 1/2] f2fs: do not set LOST_PINO for newly created dir Sheng Yong
2017-06-26  2:41 ` [RFC PATCH v2 2/2] f2fs: do not set LOST_PINO for renamed dir Sheng Yong
2017-07-01 15:10   ` Jaegeuk Kim
2017-07-02  4:09     ` Sheng Yong [this message]
2017-06-26 11:16 ` [RFC PATCH v2 1/2] f2fs: do not set LOST_PINO for newly created dir 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=c6de6bcd-2ca8-1a3b-71b7-be99ed832fb4@huawei.com \
    --to=shengyong1@huawei.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.