mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: Chao Yu <chao@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 3/5] f2fs: check in-memory block bitmap
Date: Sat, 7 Jan 2017 21:02:08 -0800	[thread overview]
Message-ID: <20170108050208.GA16864@jaegeuk.local> (raw)
In-Reply-To: <83098918-d882-8743-51bc-1e96038d6ad2@huawei.com>

Hi Chao,

On 01/07, Chao Yu wrote:
> This patch adds a mirror for valid block bitmap, and use it to detect
> in-memory bitmap corruption which may be caused by bit-transition of
> cache or memory overflow.
> 
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
>  fs/f2fs/segment.c | 30 ++++++++++++++++++++++++++++--
>  fs/f2fs/segment.h |  6 ++++++
>  2 files changed, 34 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index fa8c0ae87d47..ec21ee1c61cd 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -1026,14 +1026,32 @@ static void update_sit_entry(struct f2fs_sb_info *sbi, block_t blkaddr, int del)
> 
>  	/* Update valid block bitmap */
>  	if (del > 0) {
> -		if (f2fs_test_and_set_bit(offset, se->cur_valid_map))
> +		if (f2fs_test_and_set_bit(offset, se->cur_valid_map)) {
> +#ifdef CONFIG_F2FS_CHECK_FS
> +			if (f2fs_test_and_set_bit(offset,
> +						se->cur_valid_map_mir))
> +				f2fs_bug_on(sbi, 1);
> +			else
> +				WARN_ON(1);
> +#else
>  			f2fs_bug_on(sbi, 1);
> +#endif
> +		}
>  		if (f2fs_discard_en(sbi) &&
>  			!f2fs_test_and_set_bit(offset, se->discard_map))
>  			sbi->discard_blks--;
>  	} else {
> -		if (!f2fs_test_and_clear_bit(offset, se->cur_valid_map))
> +		if (!f2fs_test_and_clear_bit(offset, se->cur_valid_map)) {
> +#ifdef CONFIG_F2FS_CHECK_FS
> +			if (!f2fs_test_and_clear_bit(offset,
> +						se->cur_valid_map_mir))
> +				f2fs_bug_on(sbi, 1);
> +			else
> +				WARN_ON(1);
> +#else
>  			f2fs_bug_on(sbi, 1);
> +#endif
> +		}
>  		if (f2fs_discard_en(sbi) &&
>  			f2fs_test_and_clear_bit(offset, se->discard_map))
>  			sbi->discard_blks++;
> @@ -2357,6 +2375,13 @@ static int build_sit_info(struct f2fs_sb_info *sbi)
>  				!sit_i->sentries[start].ckpt_valid_map)
>  			return -ENOMEM;
> 
> +#ifdef CONFIG_F2FS_CHECK_FS
> +		sit_i->sentries[start].cur_valid_map_mir
> +			= kzalloc(SIT_VBLOCK_MAP_SIZE, GFP_KERNEL);
> +		if (!sit_i->sentries[start].cur_valid_map_mir)
> +			return -ENOMEM;
> +#endif
> +
>  		if (f2fs_discard_en(sbi)) {
>  			sit_i->sentries[start].discard_map
>  				= kzalloc(SIT_VBLOCK_MAP_SIZE, GFP_KERNEL);
> @@ -2786,6 +2811,7 @@ static void destroy_sit_info(struct f2fs_sb_info *sbi)
>  	if (sit_i->sentries) {
>  		for (start = 0; start < MAIN_SEGS(sbi); start++) {
>  			kfree(sit_i->sentries[start].cur_valid_map);

I added:

#ifdef CONFIG_F2FS_CHECK_FS

> +			kfree(sit_i->sentries[start].cur_valid_map_mir);

#endif

Thanks,

  reply	other threads:[~2017-01-08  5:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-07 10:51 Chao Yu
2017-01-08  5:02 ` Jaegeuk Kim [this message]
2017-01-09  8:42   ` [f2fs-dev] " 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=20170108050208.GA16864@jaegeuk.local \
    --to=jaegeuk@kernel.org \
    --cc=chao@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome