linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Andrei Warkentin <andrey.warkentin@gmail.com>
Cc: linux-raid@vger.kernel.org, Jonathan Brassow <jbrassow@redhat.com>
Subject: Re: [PATCH] MD: Bitmap version cleanup.
Date: Tue, 10 Apr 2012 16:14:55 +1000	[thread overview]
Message-ID: <20120410161455.49acaeea@notabene.brown> (raw)
In-Reply-To: <1326614986-30166-1-git-send-email-andrey.warkentin@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]

On Sun, 15 Jan 2012 03:09:46 -0500 Andrei Warkentin
<andrey.warkentin@gmail.com> wrote:

> bitmap_new_disk_sb() would still create V3 bitmap superblock
> with host-endian layout.
> 
> Perhaps I'm confused, but shouldn't bitmap_new_disk_sb() be
> creating a V4 bitmap superblock instead, that is portable,
> as per comment in bitmap.h? BITMAP_MINOR was also unused.
> 
> Signed-off-by: Andrei Warkentin <andrey.warkentin@gmail.com>
> ---
>  drivers/md/bitmap.c |    3 ---
>  drivers/md/bitmap.h |    2 --
>  2 files changed, 0 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/md/bitmap.c b/drivers/md/bitmap.c
> index 045e086..e786da6 100644
> --- a/drivers/md/bitmap.c
> +++ b/drivers/md/bitmap.c
> @@ -568,9 +568,6 @@ static int bitmap_new_disk_sb(struct bitmap *bitmap)
>  	bitmap->events_cleared = bitmap->mddev->events;
>  	sb->events_cleared = cpu_to_le64(bitmap->mddev->events);
>  
> -	bitmap->flags |= BITMAP_HOSTENDIAN;
> -	sb->version = cpu_to_le32(BITMAP_MAJOR_HOSTENDIAN);
> -
>  	kunmap_atomic(sb);
>  
>  	return 0;
> diff --git a/drivers/md/bitmap.h b/drivers/md/bitmap.h
> index a15436d..af588ac 100644
> --- a/drivers/md/bitmap.h
> +++ b/drivers/md/bitmap.h
> @@ -13,8 +13,6 @@
>  #define BITMAP_MAJOR_HI 4
>  #define	BITMAP_MAJOR_HOSTENDIAN 3
>  
> -#define BITMAP_MINOR 39
> -
>  /*
>   * in-memory bitmap:
>   *

Yes, you are exactly correct.  I've applied that patch (and less than three
months since you sent it - not bad [no, not bad: terrible!])

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2012-04-10  6:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-15  8:09 [PATCH] MD: Bitmap version cleanup Andrei Warkentin
2012-04-10  6:14 ` NeilBrown [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=20120410161455.49acaeea@notabene.brown \
    --to=neilb@suse.de \
    --cc=andrey.warkentin@gmail.com \
    --cc=jbrassow@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    /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).