linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: raz ben yehuda <raziebe@gmail.com>
Cc: linux raid <linux-raid@vger.kernel.org>, ofer <ofer@bitband.com>,
	yaron <yaronp@bitband.com>
Subject: Re: Subject: [PATCH 007/009]: raid10: chunk size check in run
Date: Wed, 20 May 2009 11:41:41 +1000	[thread overview]
Message-ID: <18963.24533.807740.325472@notabene.brown> (raw)
In-Reply-To: message from raz ben yehuda on Tuesday May 19

On Tuesday May 19, raziebe@gmail.com wrote:
> have raid10 check chunk size in run method instead of in md
>  raid10.c |   10 +++++++++-
>  1 file changed, 9 insertions(+), 1 deletion(-)
> Signed-off-by: raziebe@gmail.com
> diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
> index 2405add..52ad64e 100644
> --- a/drivers/md/raid10.c
> +++ b/drivers/md/raid10.c
> @@ -2055,7 +2055,15 @@ static int run(mddev_t *mddev)
>  		       "at least PAGE_SIZE(%ld).\n", PAGE_SIZE);
>  		return -EINVAL;
>  	}
> -
> +	/*
> +	 * chunk-size has to be a power of 2
> +	 */
> +	if ((1 << ffz(~mddev->chunk_size)) != mddev->chunk_size) {
> +		printk(KERN_ERR "%s chunk_size of %d not valid\n",
> +			mdname(mddev),
> +			mddev->chunk_size);
> +		return -EINVAL;
> +	}
>  	nc = mddev->layout & 255;
>  	fc = (mddev->layout >> 8) & 255;
>  	fo = mddev->layout & (1<<16);
> 

I combined this with the other chunk_size check in run, so there
is only the one printk.

Thanks,
NeilBrown

  reply	other threads:[~2009-05-20  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 16:08 Subject: [PATCH 007/009]: raid10: chunk size check in run raz ben yehuda
2009-05-20  1:41 ` Neil Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-19 16:09 raz ben yehuda
2009-05-19 16:10 raz ben yehuda
2009-05-19 16:10 raz ben yehuda
2009-05-19 16:10 raz ben yehuda

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=18963.24533.807740.325472@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=ofer@bitband.com \
    --cc=raziebe@gmail.com \
    --cc=yaronp@bitband.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).