From: bmarzins@sourceware.org
To: dm-cvs@sourceware.org, dm-devel@redhat.com
Subject: multipath-tools/multipathd main.c
Date: 10 Oct 2011 03:47:07 -0000 [thread overview]
Message-ID: <20111010034707.13284.qmail@sourceware.org> (raw)
CVSROOT: /cvs/dm
Module name: multipath-tools
Branch: RHEL5_FC6
Changes by: bmarzins@sourceware.org 2011-10-10 03:47:07
Modified files:
multipathd : main.c
Log message:
Fix for BZ# 655976. Don't automatically update path groups on devices set to
manual failback when the prio changes. This fix is already upstream.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/multipath-tools/multipathd/main.c.diff?cvsroot=dm&only_with_tag=RHEL5_FC6&r1=1.69.2.35&r2=1.69.2.36
--- multipath-tools/multipathd/main.c 2011/04/11 17:01:08 1.69.2.35
+++ multipath-tools/multipathd/main.c 2011/10/10 03:47:07 1.69.2.36
@@ -1153,8 +1153,7 @@
* path prio refreshing
*/
condlog(4, "path prio refresh");
- if (update_prio(pp, new_path_up) &&
- pp->mpp->pgpolicyfn == (pgpolicyfn *)group_by_prio)
+ if (update_prio(pp, new_path_up) && pp->mpp->pgpolicyfn == (pgpolicyfn *)group_by_prio && (pp->mpp->pgfailback == -FAILBACK_IMMEDIATE || pp->mpp->pgfailback > 0))
update_path_groups(pp->mpp, vecs, !new_path_up);
else if (need_switch_pathgroup(pp->mpp, 0)) {
if (pp->mpp->pgfailback > 0 &&
next reply other threads:[~2011-10-10 3:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 3:47 bmarzins [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-10 18:49 multipath-tools/multipathd main.c bmarzins
2012-08-07 19:37 bmarzins
2012-03-22 18:02 bmarzins
2011-10-24 13:46 bmarzins
2011-04-11 17:01 bmarzins
2010-12-07 6:02 bmarzins
2010-09-01 18:29 bmarzins
2010-08-09 16:16 bmarzins
2009-11-02 19:11 bmarzins
2009-09-10 16:27 bmarzins
2009-04-27 21:19 bmarzins
2008-10-17 18:37 bmarzins
2008-09-12 23:49 bmarzins
2008-09-04 23:31 bmarzins
2008-05-12 18:48 bmarzins
2007-04-26 17:47 bmarzins
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=20111010034707.13284.qmail@sourceware.org \
--to=bmarzins@sourceware.org \
--cc=dm-cvs@sourceware.org \
--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).