linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Yunlong Song <sylinux@163.com>, Chao Yu <chao@kernel.org>
Cc: Yunlong Song <yunlong.song@huawei.com>,
	jaegeuk <jaegeuk@kernel.org>, miaoxie <miaoxie@huawei.com>,
	"bintian.wang" <bintian.wang@huawei.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] f2fs: update cur_valid_map_mir together with cur_valid_map
Date: Wed, 2 Aug 2017 09:34:52 +0800	[thread overview]
Message-ID: <8be82ea4-db80-8f87-9029-e63d2926f7d1@huawei.com> (raw)
In-Reply-To: <c1935af.77af.15d9ebd35e3.Coremail.sylinux@163.com>

Hi Yunlong,

On 2017/8/2 0:59, Yunlong Song wrote:
> Hi Chao,
>     I think there is no need to test mirror bitmap when original bitmap's check
> get passed, it is an instruction waste for "test". By the way, previous patch
> uses WARN to skip trigger panic when the memory is flipped, I think it is proper
> to not trigger panic in this situation, because it is not code bug at all in
> such case.

Original idea is trying to use bitmap mirror to detect bitmap corruption caused
by memory overflow or bit-transition of cache.

So if we encounter inconsistency in between original bitmap and mirror bitmap,
there may be memory overflow or cache bit-transition, we need to detect that;
another case is that both bitmap is consistent, but we are trying to reuse valid
block address or free invalid block address, indeed that is a bug.

Below modification can cover above two cases, which make original idea of
introducing mirror bitmap check working correctly.

Thanks,

> On 08/01/2017 23:44, Chao Yu <mailto:chao@kernel.org> wrote:
> 
>     Hi Yunlong,
> 
>     How about checking consistence in between original and mirror bitmap all
>     the time as below?
> 
>     ---
>     fs/f2fs/segment.c | 41 +++++++++++++++++++++++++++--------------
>     1 file changed, 27 insertions(+), 14 deletions(-)
> 
>     diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
>     index a26c24dae70c..f32a19cf486a 100644
>     --- a/fs/f2fs/segment.c
>     +++ b/fs/f2fs/segment.c
>     @@ -1510,6 +1510,7 @@ static void update_sit_entry(struct f2fs_sb_info *sbi,
>     block_t blkaddr, int del)
>        struct seg_entry *se;
>        unsigned int segno, offset;
>        long int new_vblocks;
>     +    bool exist, mir_exist;
> 
>        segno = GET_SEGNO(sbi, blkaddr);
> 
>     @@ -1526,17 +1527,23 @@ 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)) {
>     +        exist = 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
>     +        mir_exist = f2fs_test_and_set_bit(offset,
>     +                        se->cur_valid_map_mir);
>     +        if (exist != mir_exist) {
>     +            f2fs_msg(sbi->sb, KERN_ERR, "Inconsistent error "
>     +                "when setting bitmap, blk:%u, old bit:%d",
>     +                blkaddr, exist);
>                f2fs_bug_on(sbi, 1);
>     +        }
>     #endif
>     +        if (exist) {
>     +            f2fs_msg(sbi->sb, KERN_ERR,
>     +                "Bitmap was set, blk:%u", blkaddr);
>     +            f2fs_bug_on(sbi, 1);
>            }
>     +
>            if (f2fs_discard_en(sbi) &&
>                !f2fs_test_and_set_bit(offset, se->discard_map))
>                sbi->discard_blks--;
>     @@ -1547,17 +1554,23 @@ static void update_sit_entry(struct f2fs_sb_info
>     *sbi, block_t blkaddr, int del)
>                    se->ckpt_valid_blocks++;
>            }
>        } else {
>     -        if (!f2fs_test_and_clear_bit(offset, se->cur_valid_map)) {
>     +        exist = 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
>     +        mir_exist = f2fs_test_and_clear_bit(offset,
>     +                        se->cur_valid_map_mir);
>     +        if (exist != mir_exist) {
>     +            f2fs_msg(sbi->sb, KERN_ERR, "Inconsistent error "
>     +                "when clearing bitmap, blk:%u, old bit:%d",
>     +                blkaddr, exist);
>                f2fs_bug_on(sbi, 1);
>     +        }
>     #endif
>     +        if (!exist) {
>     +            f2fs_msg(sbi->sb, KERN_ERR,
>     +                "Bitmap was cleared, blk:%u", blkaddr);
>     +            f2fs_bug_on(sbi, 1);
>            }
>     +
>            if (f2fs_discard_en(sbi) &&
>                f2fs_test_and_clear_bit(offset, se->discard_map))
>                sbi->discard_blks++;
>     -- 
>     2.13.0.90.g1eb437020
> 
>     On 2017/8/1 15:56, Yunlong Song wrote:
>     > When cur_valid_map passes the f2fs_test_and_set(,clear)_bit test,
>     > cur_valid_map_mir update is skipped unlikely, so fix it.
>     >
>     > Signed-off-by: Yunlong Song <yunlong.song@huawei.com>
>     > ---
>     >  fs/f2fs/segment.c | 8 ++++++++
>     >  1 file changed, 8 insertions(+)
>     >
>     > diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
>     > index 151968e..6f7731a 100644
>     > --- a/fs/f2fs/segment.c
>     > +++ b/fs/f2fs/segment.c
>     > @@ -1535,6 +1535,10 @@ static void update_sit_entry(struct f2fs_sb_info
>     *sbi, block_t blkaddr, int del)
>     >              f2fs_bug_on(sbi, 1);
>     >  #endif
>     >          }
>     > +#ifdef CONFIG_F2FS_CHECK_FS
>     > +        else
>     > +            f2fs_set_bit(offset, se->cur_valid_map_mir);
>     > +#endif
>     >          if (f2fs_discard_en(sbi) &&
>     >              !f2fs_test_and_set_bit(offset, se->discard_map))
>     >              sbi->discard_blks--;
>     > @@ -1556,6 +1560,10 @@ static void update_sit_entry(struct f2fs_sb_info
>     *sbi, block_t blkaddr, int del)
>     >              f2fs_bug_on(sbi, 1);
>     >  #endif
>     >          }
>     > +#ifdef CONFIG_F2FS_CHECK_FS
>     > +        else
>     > +            f2fs_clear_bit(offset, se->cur_valid_map_mir);
>     > +#endif
>     >          if (f2fs_discard_en(sbi) &&
>     >              f2fs_test_and_clear_bit(offset, se->discard_map))
>     >              sbi->discard_blks++;
>     >
> 

  parent reply	other threads:[~2017-08-02  1:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01  7:56 [PATCH] f2fs: update cur_valid_map_mir together with cur_valid_map Yunlong Song
2017-08-01 15:44 ` Chao Yu
     [not found]   ` <c1935af.77af.15d9ebd35e3.Coremail.sylinux@163.com>
2017-08-02  1:34     ` Chao Yu [this message]
2017-08-02  8:02       ` Yunlong Song
2017-08-02  8:47         ` Chao Yu
2017-08-02  9:00           ` Yunlong Song
2017-08-02 13:20 ` [PATCH v2] " Yunlong Song
2017-08-02 14:16   ` [PATCH] f2fs: do not change the valid_block value if cur_valid_map was wrongly set or cleared Yunlong Song
2017-08-05  1:23     ` [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=8be82ea4-db80-8f87-9029-e63d2926f7d1@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=bintian.wang@huawei.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=sylinux@163.com \
    --cc=yunlong.song@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).