linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shaohua Li <shli@kernel.org>
To: Guoqing Jiang <gqjiang@suse.com>
Cc: neilb@suse.com, linux-raid@vger.kernel.org
Subject: Re: [PATCH v2] md/bitmap: don't read page from device with Bitmap_sync
Date: Mon, 10 Jul 2017 10:29:45 -0700	[thread overview]
Message-ID: <20170710172945.cfbr5aidjrd5pfx2@kernel.org> (raw)
In-Reply-To: <20170704032030.27665-1-gqjiang@suse.com>

On Tue, Jul 04, 2017 at 11:20:30AM +0800, Guoqing Jiang wrote:
> The device owns Bitmap_sync flag needs recovery
> to become in sync, and read page from this type
> device could get stale status.
> 
> Also add comments for Bitmap_sync bit per the
> suggestion from Shaohua and Neil.
> 
> Previous disscussion can be found here:
> https://marc.info/?t=149760428900004&r=1&w=2
> 
> Signed-off-by: Guoqing Jiang <gqjiang@suse.com>

Applied!
> ---
>  drivers/md/bitmap.c | 3 ++-
>  drivers/md/md.h     | 4 +++-
>  2 files changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/md/bitmap.c b/drivers/md/bitmap.c
> index f4eace5..40f3cd7 100644
> --- a/drivers/md/bitmap.c
> +++ b/drivers/md/bitmap.c
> @@ -156,7 +156,8 @@ static int read_sb_page(struct mddev *mddev, loff_t offset,
>  
>  	rdev_for_each(rdev, mddev) {
>  		if (! test_bit(In_sync, &rdev->flags)
> -		    || test_bit(Faulty, &rdev->flags))
> +		    || test_bit(Faulty, &rdev->flags)
> +		    || test_bit(Bitmap_sync, &rdev->flags))
>  			continue;
>  
>  		target = offset + index * (PAGE_SIZE/512);
> diff --git a/drivers/md/md.h b/drivers/md/md.h
> index 991f0fe..b50eb4a 100644
> --- a/drivers/md/md.h
> +++ b/drivers/md/md.h
> @@ -134,7 +134,9 @@ enum flag_bits {
>  	Faulty,			/* device is known to have a fault */
>  	In_sync,		/* device is in_sync with rest of array */
>  	Bitmap_sync,		/* ..actually, not quite In_sync.  Need a
> -				 * bitmap-based recovery to get fully in sync
> +				 * bitmap-based recovery to get fully in sync.
> +				 * The bit is only meaningful before device
> +				 * has been passed to pers->hot_add_disk.
>  				 */
>  	WriteMostly,		/* Avoid reading if at all possible */
>  	AutoDetected,		/* added by auto-detect */
> -- 
> 2.10.0
> 

      reply	other threads:[~2017-07-10 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04  3:20 [PATCH v2] md/bitmap: don't read page from device with Bitmap_sync Guoqing Jiang
2017-07-10 17:29 ` Shaohua Li [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=20170710172945.cfbr5aidjrd5pfx2@kernel.org \
    --to=shli@kernel.org \
    --cc=gqjiang@suse.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;
as well as URLs for NNTP newsgroup(s).