From: Jay Vosburgh <fubar@us.ibm.com>
To: netdev@vger.kernel.org
Cc: David Miller <davem@davemloft.net>
Subject: [PATCH net-next 0/6] net/core, bonding: dev_uc_sync fixes, bonding update
Date: Thu, 30 May 2013 17:55:38 -0700 [thread overview]
Message-ID: <1369961744-21460-1-git-send-email-fubar@us.ibm.com> (raw)
This patch set includes 6 patches: four fixes to the dev_mc_sync /
dev_mc_unsync system; and two patches to bonding, one to utilize the sync
/ unsync functions, and another minor fix related to MAC address handling.
A brief description of each patch:
1. uninitialized variable in __hw_addr_create_ex
2. __hw_addr_unsync_one does not work because "from" addresses
aren't marked as "synced."
3. __hw_addr_sync_one as called by __hw_addr_sync_multiple will
not remove references properly
4. dev_mc_sync_multiple doesn't call the _multiple helper function
5. Convert bonding to use dev_{mc,uc}_sync / unsync
6. Disallow changes of bonding MAC if fail_over_mac is set to
"follow".
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next reply other threads:[~2013-05-31 0:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 0:55 Jay Vosburgh [this message]
2013-05-31 0:55 ` [PATCH net-next 1/6] net/core: __hw_addr_create_ex does not initialize sync_cnt Jay Vosburgh
2013-05-31 0:55 ` [PATCH net-next 2/6] net/core: __hw_addr_unsync_one refcount leak synced Jay Vosburgh
2013-05-31 0:55 ` [PATCH net-next 3/6] net/core: __hw_addr_sync_one / _multiple broken Jay Vosburgh
2013-05-31 0:55 ` [PATCH net-next 4/6] net/core: dev_mc_sync_multiple calls wrong helper Jay Vosburgh
2013-05-31 0:55 ` [PATCH net-next 5/6] bonding: Convert hw addr handling to sync/unsync, support ucast addresses Jay Vosburgh
2013-05-31 0:55 ` [PATCH net-next 6/6] bonding: disallow change of MAC if fail_over_mac enabled Jay Vosburgh
2013-05-31 8:31 ` [PATCH net-next 0/6] net/core, bonding: dev_uc_sync fixes, bonding update David Miller
2013-05-31 15:28 ` Shawn Bohrer
2013-05-31 15:56 ` Jay Vosburgh
2013-05-31 16:01 ` Vlad Yasevich
2013-05-31 17:27 ` Jay Vosburgh
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=1369961744-21460-1-git-send-email-fubar@us.ibm.com \
--to=fubar@us.ibm.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).