ofproto-dpif: Do not dpif_port_del() patch ports in port_del().
authorBen Pfaff <blp@nicira.com>
Fri, 30 Aug 2013 03:55:10 +0000 (20:55 -0700)
committerBen Pfaff <blp@nicira.com>
Wed, 4 Sep 2013 22:52:08 +0000 (15:52 -0700)
commit06c1b106842e730af13b8a8246f7c2d26665115d
tree681a6c51b5a08872f42abba8ae275012502fd8d8
parent2ea2648141fba06cd6f81c00fc831de6afcc20e9
ofproto-dpif: Do not dpif_port_del() patch ports in port_del().

Patch ports don't have datapath ports so it doesn't make sense to try to
call dpif_port_del() on them.  If we do try, it will fail, which makes the
caller think that the port wasn't really deleted, which in turn keeps
ofproto from reporting the port deletion via OpenFlow.  This fixes the
problem.

Without this patch, the following commands, executed under "make sandbox",
will report the patch port addition in "ovs-ofctl monitor" output, but not
the patch port deletion.  With this patch, both the addition and deletion
will be reported.

    ovs-vsctl add-br br0 -- set bridge br0 datapath_type=netdev
    ovs-ofctl monitor br0 128 &
    ovs-vsctl add-port br0 patch1 \
        -- set interface patch1 type=patch options:peer=patch2 \
        -- add-port br0 patch2 \
        -- set interface patch2 type=patch options:peer=patch1
    ovs-vsctl del-port patch1
    ovs-vsctl del-port patch2

Reported-by: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Signed-off-by: Ben Pfaff <blp@nicira.com>
ofproto/ofproto-dpif.c