linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: majianpeng <majianpeng@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Re: [PATCH 2/5] md:Add place to update ->recovery_cp.
Date: Mon, 29 Oct 2012 09:30:27 +0800	[thread overview]
Message-ID: <201210290930240779147@gmail.com> (raw)
In-Reply-To: 20121029083529.78c2024e@notabene.brown

>On Sat, 27 Oct 2012 10:28:18 +0800 kernelmail <kedacomkernel@gmail.com> wrote:
>
>> In resyncing, recovery_cp only updated when resync aborted or completed.
>> But in md drives,many place used it to judge.So add a place to update.
>> 
>> Signed-off-by: Jianpeng Ma <majianpeng@gmail.com>
>> ---
>>  drivers/md/md.c |    2 ++
>>  1 file changed, 2 insertions(+)
>> 
>> diff --git a/drivers/md/md.c b/drivers/md/md.c
>> index 1d9940d..01e25bd 100644
>> --- a/drivers/md/md.c
>> +++ b/drivers/md/md.c
>> @@ -7454,6 +7454,8 @@ void md_do_sync(struct md_thread *thread)
>>  			wait_event(mddev->recovery_wait,
>>  				   atomic_read(&mddev->recovery_active) == 0);
>>  			mddev->curr_resync_completed = j;
>> +			if (test_bit(MD_RECOVERY_SYNC, &mddev->recovery))
>> +				mddev->recovery_cp = j;
>>  			set_bit(MD_CHANGE_CLEAN, &mddev->flags);
>>  			sysfs_notify(&mddev->kobj, NULL, "sync_completed");
>>  		}
>
>This isn't correct.  If MD_RECOVERY_REQUESTED, then j might be less than
>recovery_cp and we don't want to reduce recovery_cp.
>
>If you would like to fix that (i.e. only set recovery_cp if it is less than
>'j'), then I'll apply the patch.
>
>NeilBrown
>
Ok, i'll modify and resend to you.
Thanks!
Jianpeng

      reply	other threads:[~2012-10-29  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-27  2:28 [PATCH 2/5] md:Add place to update ->recovery_cp kernelmail
2012-10-28 21:35 ` NeilBrown
2012-10-29  1:30   ` majianpeng [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=201210290930240779147@gmail.com \
    --to=majianpeng@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).