From: "Benjamin Marzinski" <bmarzins@redhat.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Christophe Varoqui <christophe.varoqui@gmail.com>
Subject: Re: [PATCH] multipathd: restore paths after reconfigure
Date: Thu, 21 Jul 2016 12:58:29 -0500 [thread overview]
Message-ID: <20160721175829.GR8095@octiron.msp.redhat.com> (raw)
In-Reply-To: <758f2ab7-c8ed-06d9-f891-5cdaf893a5a7@sandisk.com>
On Thu, Jul 21, 2016 at 09:29:37AM -0700, Bart Van Assche wrote:
> On 07/01/2016 02:46 PM, Benjamin Marzinski wrote:
> >multipathd has code to finish gathering the information of paths that
> >were not active at the time they were discovered. When the checker loop
> >goes to check a path, and notices that it wasn't fully initialized, it
> >is supposed to complete the initialization. However the code is broken.
> >This means that if you reconfigure multipathd while paths are down, they
> >will no longer be usable. This patch makes sure that check_path will
> >actually rerun pathinfo to finish setting up the path, so that after the
> >path comes back up, it will be usable again.
> >[ ... ]
> >@@ -1779,7 +1785,13 @@ checkerloop (void *ap)
> > lock(vecs->lock);
> > pthread_testcancel();
> > vector_foreach_slot (vecs->pathvec, pp, i) {
> >- num_paths += check_path(vecs, pp, ticks);
> >+ rc = check_path(vecs, pp, ticks);
> >+ if (rc < 0) {
> >+ vector_del_slot(vecs->pathvec, i);
> >+ free_path(pp);
> >+ i--;
> >+ } else;
> >+ num_paths += rc;
> > }
> > lock_cleanup_pop(vecs->lock);
> > }
>
> Hi Ben,
>
> Was the semicolon after the "else" intended or was it a typo?
Oops! That was a typo. I'll send off a quick patch. Thanks for catching
that.
-Ben
>
> Thanks,
>
> Bart.
prev parent reply other threads:[~2016-07-21 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 21:46 [PATCH] multipathd: restore paths after reconfigure Benjamin Marzinski
2016-07-08 7:21 ` Christophe Varoqui
2016-07-21 16:29 ` Bart Van Assche
2016-07-21 17:58 ` Benjamin Marzinski [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=20160721175829.GR8095@octiron.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=bart.vanassche@sandisk.com \
--cc=christophe.varoqui@gmail.com \
--cc=dm-devel@redhat.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).