Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: NeilBrown <neilb@suse.com>
Cc: Dan Russell <dpr@aol.com>, linux-raid@vger.kernel.org
Subject: Re: [PATCH mdadm] ddf: use 64bit 'size', not 32bit 'info->size' for create.
Date: Thu, 10 Mar 2016 11:43:46 -0500	[thread overview]
Message-ID: <wrfjio0u1dx9.fsf@redhat.com> (raw)
In-Reply-To: <87a8m6ke0c.fsf@notabene.neil.brown.name> (NeilBrown's message of "Thu, 10 Mar 2016 18:06:59 +1100")

NeilBrown <neilb@suse.com> writes:
> The 'size' field of mdu_disk_info_t is 32bit and should not be used
> except for legacy ioctls.  super-ddf got this wrong :-(
>
> This change makes it possible to create ddf arrays which used more than
> 2TB of each device.
>
> Reported-by: Dan Russell <dpr@aol.com>
> Signed-off-by: NeilBrown <neilb@suse.com>
> ---
>  super-ddf.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/super-ddf.c b/super-ddf.c
> index faaf0a7ca9e0..0e00d17dd169 100644
> --- a/super-ddf.c
> +++ b/super-ddf.c
> @@ -2688,10 +2688,10 @@ static int init_super_ddf_bvd(struct supertype *st,
>  		free(vcl);
>  		return 0;
>  	}
> -	vc->blocks = cpu_to_be64(info->size * 2);
> +	vc->blocks = cpu_to_be64(size * 2);
>  	vc->array_blocks = cpu_to_be64(
>  		calc_array_size(info->level, info->raid_disks, info->layout,
> -				info->chunk_size, info->size*2));
> +				info->chunk_size, size*2));
>  	memset(vc->pad1, 0xff, 8);
>  	vc->spare_refs[0] = cpu_to_be32(0xffffffff);
>  	vc->spare_refs[1] = cpu_to_be32(0xffffffff);

Thanks for the fix! I applied it with a small mod, adding the missing
spaces in the last line:

> +				info->chunk_size, size * 2));

Cheers,
Jes

      reply	other threads:[~2016-03-10 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10  7:06 [PATCH mdadm] ddf: use 64bit 'size', not 32bit 'info->size' for create NeilBrown
2016-03-10 16:43 ` Jes Sorensen [this message]

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=wrfjio0u1dx9.fsf@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=dpr@aol.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.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