From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, yuchao0@huawei.com,
liushuoran@huawei.com
Subject: Re: [PATCH 2/2] f2fs: don't skip recovering inode depend on i_times
Date: Thu, 3 Nov 2016 11:02:33 -0700 [thread overview]
Message-ID: <20161103180233.GC76264@jaegeuk> (raw)
In-Reply-To: <20161103162656.2982-2-chao@kernel.org>
On Fri, Nov 04, 2016 at 12:26:56AM +0800, Chao Yu wrote:
> From: Chao Yu <yuchao0@huawei.com>
>
> i_times of inode will be set with current system time which can be
> configured through 'date', so it's not safe to judge dnode block as
> garbage data depend on i_times.
This is not to detect garbage data, but to skip redundant unchanged inode.
Anyway, in the code part, looks good to me.
Thanks,
>
> Now, we have used enhanced 'cp_ver + cp' crc method to verify valid
> dnode block, so I expect recoverying invalid dnode is almost not
> possible.
>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
> fs/f2fs/recovery.c | 31 +------------------------------
> 1 file changed, 1 insertion(+), 30 deletions(-)
>
> diff --git a/fs/f2fs/recovery.c b/fs/f2fs/recovery.c
> index d2ba4da..62523b2 100644
> --- a/fs/f2fs/recovery.c
> +++ b/fs/f2fs/recovery.c
> @@ -196,32 +196,6 @@ static void recover_inode(struct inode *inode, struct page *page)
> ino_of_node(page), name);
> }
>
> -static bool is_same_inode(struct inode *inode, struct page *ipage)
> -{
> - struct f2fs_inode *ri = F2FS_INODE(ipage);
> - struct timespec disk;
> -
> - if (!IS_INODE(ipage))
> - return true;
> -
> - disk.tv_sec = le64_to_cpu(ri->i_ctime);
> - disk.tv_nsec = le32_to_cpu(ri->i_ctime_nsec);
> - if (timespec_compare(&inode->i_ctime, &disk) > 0)
> - return false;
> -
> - disk.tv_sec = le64_to_cpu(ri->i_atime);
> - disk.tv_nsec = le32_to_cpu(ri->i_atime_nsec);
> - if (timespec_compare(&inode->i_atime, &disk) > 0)
> - return false;
> -
> - disk.tv_sec = le64_to_cpu(ri->i_mtime);
> - disk.tv_nsec = le32_to_cpu(ri->i_mtime_nsec);
> - if (timespec_compare(&inode->i_mtime, &disk) > 0)
> - return false;
> -
> - return true;
> -}
> -
> static int find_fsync_dnodes(struct f2fs_sb_info *sbi, struct list_head *head)
> {
> struct curseg_info *curseg;
> @@ -248,10 +222,7 @@ static int find_fsync_dnodes(struct f2fs_sb_info *sbi, struct list_head *head)
> goto next;
>
> entry = get_fsync_inode(head, ino_of_node(page));
> - if (entry) {
> - if (!is_same_inode(entry->inode, page))
> - goto next;
> - } else {
> + if (!entry) {
> if (IS_INODE(page) && is_dent_dnode(page)) {
> err = recover_inode_page(sbi, page);
> if (err)
> --
> 2.10.1
next prev parent reply other threads:[~2016-11-03 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 16:26 [PATCH 1/2] f2fs: fix wrong i_atime recovery Chao Yu
2016-11-03 16:26 ` [PATCH 2/2] f2fs: don't skip recovering inode depend on i_times Chao Yu
2016-11-03 18:02 ` Jaegeuk Kim [this message]
2016-11-04 8:30 ` Chao Yu
2016-11-04 22:53 ` Jaegeuk Kim
2016-11-05 3:12 ` Chao Yu
2016-11-05 7:02 ` 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=20161103180233.GC76264@jaegeuk \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=liushuoran@huawei.com \
--cc=yuchao0@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).