Netdev List
 help / color / mirror / Atom feed
From: Andy Gospodarek <andy@greyhouse.net>
To: Andy Gospodarek <andy@greyhouse.net>
Cc: netdev@vger.kernel.org,
	Vitalii Demianets <vitas@nppfactor.kiev.ua>,
	Jay Vosburgh <fubar@us.ibm.com>, Takuma Umeya <tumeya@redhat.com>
Subject: Re: [PATCH net-next v2] bonding: fix string comparison errors
Date: Tue, 26 Jul 2011 17:08:30 -0400	[thread overview]
Message-ID: <20110726210829.GQ21309@gospo.rdu.redhat.com> (raw)
In-Reply-To: <1311714479-9260-1-git-send-email-andy@greyhouse.net>

On Tue, Jul 26, 2011 at 05:07:59PM -0400, Andy Gospodarek wrote:
> When a bond contains a device where one name is the subset of another
> (eth1 and eth10, for example), one cannot properly set the primary
> device or the currently active device.
> 
> This was reported and based on work by Takuma Umeya.  I also verified
> the problem and tested that this fix resolves it.
> 
> V2: A few did not like the the current code or my changes, so I
> re-factored bonding_store_primary and bonding_store_active_slave to be a
> bit cleaner, dropped the use of strnicmp since we did not really need
> the comparison to be case insensitive, and formatted the input string
> from sysfs so a comparison to IFNAMSIZ could be used.
> 
> I also discovered an error in bonding_store_active_slave that would
> modify bond->primary_slave rather than bond->curr_active_slave before
> forcing the bonding driver to choose a new active slave.
> 

Sorry I apparently cannot properly use git send-email. :-)


  reply	other threads:[~2011-07-26 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 21:07 [PATCH net-next v2] bonding: fix string comparison errors Andy Gospodarek
2011-07-26 21:08 ` Andy Gospodarek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-07-26 20:51 Andy Gospodarek

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=20110726210829.GQ21309@gospo.rdu.redhat.com \
    --to=andy@greyhouse.net \
    --cc=fubar@us.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=tumeya@redhat.com \
    --cc=vitas@nppfactor.kiev.ua \
    /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