From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Wanpeng Li <wanpeng.li@linux.intel.com>
Cc: Changman Lee <cm224.lee@samsung.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: fix recover orphan inodes
Date: Wed, 25 Feb 2015 10:35:23 -0800 [thread overview]
Message-ID: <20150225183403.GA51593@jaegeuk-mac02.mot.com> (raw)
In-Reply-To: <1424840017-97604-1-git-send-email-wanpeng.li@linux.intel.com>
Hi Wanpeng,
On Wed, Feb 25, 2015 at 12:53:37PM +0800, Wanpeng Li wrote:
> recover_orphan_inodes is used to recover orphan inodes, the meta pages
> which readahead should be orphan_blkaddr - start_blk instead of orphan_blkaddr.
> This patch fix it.
>
> Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com>
> ---
> fs/f2fs/checkpoint.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
> index e6c271f..0f42ff3 100644
> --- a/fs/f2fs/checkpoint.c
> +++ b/fs/f2fs/checkpoint.c
> @@ -468,9 +468,9 @@ void recover_orphan_inodes(struct f2fs_sb_info *sbi)
> le32_to_cpu(F2FS_RAW_SUPER(sbi)->cp_payload);
Actually it seems the name, orphan_blkaddr, was wrong.
That should be orphan_blocks which is no need to fix like this.
Instead, I found there is another bug below.
> orphan_blkaddr = __start_sum_addr(sbi) - 1;
orphan_blocks = __start_sum_addr(sbi) - 1 -
le32_to_cpu(F2FS_RAW_SUPER(sbi)->cp_payload);
It may help to define a macro to get cp_payload.
>
> - ra_meta_pages(sbi, start_blk, orphan_blkaddr, META_CP);
> + ra_meta_pages(sbi, start_blk, orphan_blkaddr - start_blk, META_CP);
The orphan_blocks is enough. No need to fix this.
>
> - for (i = 0; i < orphan_blkaddr; i++) {
> + for (i = 0; i < orphan_blkaddr - start_blk; i++) {
ditto.
Thanks,
next prev parent reply other threads:[~2015-02-25 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 4:53 Wanpeng Li
2015-02-25 18:35 ` Jaegeuk Kim [this message]
2015-02-25 23:04 ` Wanpeng Li
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=20150225183403.GA51593@jaegeuk-mac02.mot.com \
--to=jaegeuk@kernel.org \
--cc=cm224.lee@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wanpeng.li@linux.intel.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
all inboxes | Powered by JetHome®