[ovs-dev] [ovs-discuss] Please cherry-pick 8e04c6e to the 2.0 branch

Ben Pfaff blp at nicira.com
Mon Dec 2 17:31:33 UTC 2013


On Mon, Dec 02, 2013 at 03:03:17PM +0400, Andrey Korolyov wrote:
> Is there are any reasons to not cherry-pick mentioned change from the
> master? It may scare users who uses datapath version from branch and the
> fix almost clearly is harmless.

Looking at that commit, it's the following datapath commit, so Jesse
or Pravin are the right ones to make the call on a backport.

commit 8e04c6e10c28e42c715eb9fef749554c123bddbc
Author: Alexei Starovoitov <ast at plumgrid.com>
Date:   Wed Oct 16 15:28:23 2013 -0700

    datapath: fix vport-netdev unregister
    
    The combination of two commits:
    commit 8e4e1713e4
    ("openvswitch: Simplify datapath locking.")
    commit 2537b4dd0a
    ("openvswitch:: link upper device for port devices")
    
    introduced a bug where upper_dev wasn't unlinked upon
    netdev_unregister notification
    
    The following steps:
    
      modprobe openvswitch
      ovs-dpctl add-dp test
      ip tuntap add dev tap1 mode tap
      ovs-dpctl add-if test tap1
      ip tuntap del dev tap1 mode tap
...



More information about the dev mailing list