From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH 1/2] f2fs: don't need to update inode checksum for recovery
Date: Fri, 1 Sep 2017 10:25:10 -0700 [thread overview]
Message-ID: <20170901172511.7045-1-jaegeuk@kernel.org> (raw)
This patch fixes "f2fs: support inode checksum".
The recovered inode page will be rewritten with valid checksum.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/node.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index 2654c9166fba..388a00262a5f 100644
--- a/fs/f2fs/node.c
+++ b/fs/f2fs/node.c
@@ -2287,8 +2287,6 @@ int recover_inode_page(struct f2fs_sb_info *sbi, struct page *page)
F2FS_FITS_IN_INODE(src, le16_to_cpu(src->i_extra_isize),
i_projid))
dst->i_projid = src->i_projid;
-
- f2fs_inode_chksum_set(sbi, ipage);
}
new_ni = old_ni;
--
2.14.0.rc1.383.gd1ce394fe2-goog
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH 1/2] f2fs: don't need to update inode checksum for recovery
Date: Fri, 1 Sep 2017 10:25:10 -0700 [thread overview]
Message-ID: <20170901172511.7045-1-jaegeuk@kernel.org> (raw)
This patch fixes "f2fs: support inode checksum".
The recovered inode page will be rewritten with valid checksum.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/node.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index 2654c9166fba..388a00262a5f 100644
--- a/fs/f2fs/node.c
+++ b/fs/f2fs/node.c
@@ -2287,8 +2287,6 @@ int recover_inode_page(struct f2fs_sb_info *sbi, struct page *page)
F2FS_FITS_IN_INODE(src, le16_to_cpu(src->i_extra_isize),
i_projid))
dst->i_projid = src->i_projid;
-
- f2fs_inode_chksum_set(sbi, ipage);
}
new_ni = old_ni;
--
2.14.0.rc1.383.gd1ce394fe2-goog
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next reply other threads:[~2017-09-01 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 17:25 Jaegeuk Kim [this message]
2017-09-01 17:25 ` [PATCH 1/2] f2fs: don't need to update inode checksum for recovery Jaegeuk Kim
2017-09-01 17:25 ` [PATCH 2/2] f2fs: don't check inode's checksum if it was dirtied or writebacked Jaegeuk Kim
2017-09-01 17:25 ` Jaegeuk Kim
2017-09-04 1:33 ` [f2fs-dev] " Chao Yu
2017-09-04 1:33 ` Chao Yu
2017-09-04 1:26 ` [f2fs-dev] [PATCH 1/2] f2fs: don't need to update inode checksum for recovery Chao Yu
2017-09-04 1:26 ` 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=20170901172511.7045-1-jaegeuk@kernel.org \
--to=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 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.