From: "Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: Veaceslav Falico <vfalico@redhat.com>,
netdev@vger.kernel.org, Jay Vosburgh <fubar@us.ibm.com>,
Guus Sliepen <guus@debian.org>
Subject: Re: [PATCH] bonding: Don't allow mode change via sysfs with slaves present
Date: Thu, 17 Nov 2011 22:28:24 +0100 [thread overview]
Message-ID: <4EC57C78.4040006@gmail.com> (raw)
In-Reply-To: <20111116220200.GF25132@gospo.rdu.redhat.com>
Le 16/11/2011 23:02, Andy Gospodarek a écrit :
<snip>
> I was looking at ifenslave 1.1.0-20. If you look at Debian bug #641250
> you will see a very similar report to what prompted Veaceslav to come up
> with this patch and post it here.
I completely missed this version. I recently reinstalled my system and forgot to add unstable to
source.list.
> ifenslave-2.6 (1.1.0-20) unstable; urgency=low
>
> * Use dashes consistently for bonding options in README.Debian.
> Closes: #639244
> * Enslave slaves only after fully setting up the master. Closes: #641250
> * Add build-arch and build-indep targets to debian/rules.
>
> -- Guus Sliepen<guus@debian.org> Mon, 14 Nov 2011 11:36:21 +0100
Having a look at the change made to fix the bug described in #641250, I anticipate it will cause
some regressions because some of the actions taken in setup_master must be done after enslavement
and are now done before:
- primary must be set after mode (because only supported in some modes) and after enslavement.
- primary_reselect should be set after mode (because only supported in some modes), after
enslavement and after primary.
- queue_id must be set after enslavement.
- active_slave must be set after mode and after enslavement.
I will prepare a -21 version.
<snip>
> Since this problem seems like a pretty major problem and now Debian,
> Fedora, RHEL, and Ubuntu all seem to have proper initialization scripts
> to handle it, I stand behind my original ACK.
You are right.
Acked-by: Nicolas de Pesloüan <nicolas.2p.debian@free.fr>
Nicolas.
next prev parent reply other threads:[~2011-11-17 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 16:44 [PATCH] bonding: Don't allow mode change via sysfs with slaves present Veaceslav Falico
2011-11-15 17:00 ` Andy Gospodarek
2011-11-15 19:24 ` Nicolas de Pesloüan
2011-11-15 19:33 ` Ben Hutchings
2011-11-15 19:35 ` Andy Gospodarek
2011-11-15 20:02 ` Nicolas de Pesloüan
2011-11-15 20:47 ` Andy Gospodarek
2011-11-16 12:02 ` Nicolas de Pesloüan
2011-11-16 22:02 ` Andy Gospodarek
2011-11-17 1:16 ` Flavio Leitner
2011-11-17 21:28 ` Nicolas de Pesloüan [this message]
2011-11-15 21:04 ` Veaceslav Falico
2011-11-17 21:04 ` David Miller
2011-11-17 22:36 ` Nicolas de Pesloüan
2011-11-18 0:32 ` David Miller
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=4EC57C78.4040006@gmail.com \
--to=nicolas.2p.debian@gmail.com \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--cc=guus@debian.org \
--cc=netdev@vger.kernel.org \
--cc=vfalico@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.