From: NeilBrown <neilb@suse.com>
To: Shaohua Li <shli@fb.com>, linux-raid@vger.kernel.org
Cc: artur.paszkiewicz@intel.com
Subject: Re: [PATCH 1/2] RAID5: check_reshape() shouldn't call mddev_suspend
Date: Fri, 26 Feb 2016 09:08:40 +1100 [thread overview]
Message-ID: <87a8mol9xz.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <b228d35f9a8e94969d667edbcc9d7f613d706b02.1456424579.git.shli@fb.com>
[-- Attachment #1: Type: text/plain, Size: 2606 bytes --]
On Fri, Feb 26 2016, Shaohua Li wrote:
> check_reshape() is called from raid5d thread. raid5d thread shouldn't
> call mddev_suspend(), because mddev_suspend() waits for all IO finish
> but IO is handled in raid5d thread, we could easily deadlock here.
>
> Artur,
> It would be great if you can verify this works for your test.
>
> Reported-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
> Cc: NeilBrown <neilb@suse.com>
> Signed-off-by: Shaohua Li <shli@fb.com>
> ---
> drivers/md/raid5.c | 18 ++++++++++++++++++
> drivers/md/raid5.h | 2 ++
> 2 files changed, 20 insertions(+)
>
> diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
> index 7f770b0..c7fd070 100644
> --- a/drivers/md/raid5.c
> +++ b/drivers/md/raid5.c
> @@ -2089,6 +2089,14 @@ static int resize_chunks(struct r5conf *conf, int new_disks, int new_sectors)
> unsigned long cpu;
> int err = 0;
>
> + /*
> + * Never shrink. And mddev_suspend() could deadlock if this is called
> + * from raid5d. In that case, scribble_disks and scribble_sectors
> + * should equal to new_disks and new_sectors
> + */
> + if (conf->scribble_disks >= new_disks &&
> + conf->scribble_sectors >= new_sectors)
> + return 0;
> mddev_suspend(conf->mddev);
> get_online_cpus();
> for_each_present_cpu(cpu) {
> @@ -2110,6 +2118,10 @@ static int resize_chunks(struct r5conf *conf, int new_disks, int new_sectors)
> }
> put_online_cpus();
> mddev_resume(conf->mddev);
> + if (!err) {
> + conf->scribble_disks = new_disks;
> + conf->scribble_sectors = new_sectors;
> + }
> return err;
> }
>
> @@ -6413,6 +6425,12 @@ static int raid5_alloc_percpu(struct r5conf *conf)
> }
> put_online_cpus();
>
> + if (!err) {
> + conf->scribble_disks = max(conf->raid_disks,
> + conf->previous_raid_disks);
> + conf->scribble_sectors = max(conf->chunk_sectors,
> + conf->prev_chunk_sectors) / STRIPE_SECTORS;
Here we set ->scribble_sectors to a number of stripes rather than a
number of sectors. I think you need to remove the "/ STRIPE_SECTORS".
Otherwise:
Reviewed-by: NeilBrown <neilb@suse.com>
Thanks,
NeilBrown
> + }
> return err;
> }
>
> diff --git a/drivers/md/raid5.h b/drivers/md/raid5.h
> index a415e1c..ae6068d 100644
> --- a/drivers/md/raid5.h
> +++ b/drivers/md/raid5.h
> @@ -510,6 +510,8 @@ struct r5conf {
> * conversions
> */
> } __percpu *percpu;
> + int scribble_disks;
> + int scribble_sectors;
> #ifdef CONFIG_HOTPLUG_CPU
> struct notifier_block cpu_notify;
> #endif
> --
> 2.6.5
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-02-25 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 18:45 [PATCH 1/2] RAID5: check_reshape() shouldn't call mddev_suspend Shaohua Li
2016-02-25 18:45 ` [PATCH 2/2] MD: warn for potential deadlock Shaohua Li
2016-02-25 22:08 ` NeilBrown [this message]
2016-02-26 10:47 ` [PATCH 1/2] RAID5: check_reshape() shouldn't call mddev_suspend Artur Paszkiewicz
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=87a8mol9xz.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=artur.paszkiewicz@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=shli@fb.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).