Hi! I have not sent it to the upstream stable mailing list. If that would be the proper place, I'd be happy to submit it there instead. This is my first patch submission and since the original patch came from kernel.org (but for the 3.8+ kernel series only) I wasn't sure where would be the correct place to submit a backport for 3.0 thru 3.4. From reading the submission docs, I thought this would be correct.
Please advise. Thanks!! On Thu, Jan 10, 2013 at 3:45 PM, Joseph Salisbury <[email protected]> wrote: > Can you provide some information on the status of the patch with regards > to getting it merged in upstream stable? Has it been sent to the > upstream stable mailing list? > > People affected by this bug are probably wondering why the kernel team > doesn't just apply the patch and fix it. The reason is that the kernel > team is reluctant (not opposed) to apply any patch to a stable kernel > that is not from upstream. Applying patches that don't come from > upstream add greatly to the support of the kernel as other upstream > patches may touch the same area as the non-upstream patch and may > prevent them from applying cleanly. > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) > Status: Incomplete => Triaged > > ** Tags added: kernel-da-key > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1098302 > > Title: > Bonding mode Balance-ALB stomps VM MACs > > Status in “linux” package in Ubuntu: > Triaged > > Bug description: > This issue was fixed in the 3.8 kernel series; I have backported the > appropriate patch (as directed by the netdev kernel list) to the 3.0 > kernel and it worked successfully on several machines. I have built > but NOT tested this patch against 3.2 and 3.4 kernels. The patch > appears to require minor modification for inclusion in the 3.7 kernel > series. The issue resolved is as follows: > > This issue affects (at the least) virtual machines running under KVM > and using bridging to connect to a network, when that bridge > communicates over a bond using mode-6 (balance-alb). To replicate, > configure a bond of 1 or more adapters with mode-6 and bridge over > that bond. Configure a virtual machine (in my instance, I used KVM) > to place its vnet adapter under the same bridge. With the VM running, > ping the virtual machine from a remote host and check the ARP cache on > the remote host. You will find that the MAC reported for the virtual > machine will not be its configured MAC, but the MAC of one of the > bond's slaves. This causes intermittent and significant connectivity > losses (both to and from the virtual machine). > > The patch modifies the balance-alb bonding driver to leave non-local > MACs unmodified. After application, a repeat of the above test should > result in the virtual machine's correct MAC being reported in the ARP > cache of the remote host. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1098302/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098302 Title: Bonding mode Balance-ALB stomps VM MACs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1098302/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
