linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "heming.zhao@suse.com" <heming.zhao@suse.com>
To: Xiao Ni <xni@redhat.com>, jes@trained-monkey.org
Cc: ncroxon@redhat.com, heinzm@redhat.com, linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/1] mdadm/bitmap: locate bitmap calcuate bitmap position wrongly
Date: Wed, 28 Oct 2020 20:29:20 +0800	[thread overview]
Message-ID: <95046dfe-c770-8950-c720-6b1d30bb1789@suse.com> (raw)
In-Reply-To: <1603865064-27404-1-git-send-email-xni@redhat.com>

Hello Xiao,

My review comment:
You code only work in modern system. the boundary is 4k not 512, because using hardcode 4k to call calc_bitmap_size

In current cluster env, if bitmap area beyond 4K size (or 512 in very old system), locate_bitmap1 
will return wrong address.

Please refer write_bitmap1() to saparate 512 & 4096 case.

On 10/28/20 2:04 PM, Xiao Ni wrote:
> Now it only adds bitmap offset based on cluster nodes. It's not right. It needs to
> add per node bitmap space to find next node bitmap position.
> 
> Signed-off-by: Xiao Ni <xni@redhat.com>
> ---
>   super1.c | 12 +++++++++---
>   1 file changed, 9 insertions(+), 3 deletions(-)
> 
> diff --git a/super1.c b/super1.c
> index 8b0d6ff..b5b379b 100644
> --- a/super1.c
> +++ b/super1.c
> @@ -2582,8 +2582,9 @@ add_internal_bitmap1(struct supertype *st,
>   
>   static int locate_bitmap1(struct supertype *st, int fd, int node_num)
>   {
> -	unsigned long long offset;
> +	unsigned long long offset, bm_sectors_per_node;
>   	struct mdp_superblock_1 *sb;
> +	bitmap_super_t *bms;
>   	int mustfree = 0;
>   	int ret;
>   
> @@ -2598,8 +2599,13 @@ static int locate_bitmap1(struct supertype *st, int fd, int node_num)
>   		ret = 0;
>   	else
>   		ret = -1;
> -	offset = __le64_to_cpu(sb->super_offset);
> -	offset += (int32_t) __le32_to_cpu(sb->bitmap_offset) * (node_num + 1);
> +
> +	offset = __le64_to_cpu(sb->super_offset) + __le32_to_cpu(sb->bitmap_offset);
> +	if (node_num) {
> +		bms = (bitmap_super_t*)(((char*)sb)+MAX_SB_SIZE);
> +		bm_sectors_per_node = calc_bitmap_size(bms, 4096) >> 9;
> +		offset += bm_sectors_per_node * node_num;
> +	}
>   	if (mustfree)
>   		free(sb);
>   	lseek64(fd, offset<<9, 0);
> 


  reply	other threads:[~2020-10-28 21:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28  6:04 [PATCH 1/1] mdadm/bitmap: locate bitmap calcuate bitmap position wrongly Xiao Ni
2020-10-28 12:29 ` heming.zhao [this message]
2020-10-30  5:53   ` Xiao Ni
2020-10-30  6:44     ` heming.zhao
2020-11-25 23:18       ` Jes Sorensen
2020-11-26  1:43         ` heming.zhao
2021-02-26 22:00           ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2020-10-28  5:57 Xiao Ni

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=95046dfe-c770-8950-c720-6b1d30bb1789@suse.com \
    --to=heming.zhao@suse.com \
    --cc=heinzm@redhat.com \
    --cc=jes@trained-monkey.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=ncroxon@redhat.com \
    --cc=xni@redhat.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).