{"push_id":2421030960,"size":1,"distinct_size":1,"ref":"refs/heads/branch-2.8","head":"16596279409827b2e0af2420888d7024d10ab99d","before":"9f97b4555879317521a950d0dcdf961baa98e053","commits":[{"sha":"16596279409827b2e0af2420888d7024d10ab99d","author":{"name":"Ben Pfaff","email":"b30031e87fea8687a432a5f632461bee2630c54c@ovn.org"},"message":"odp-util: Print eth() for Ethernet flows if packet_type is absent.\n\nOVS datapaths have two different ways to indicate what kind of packet a\nflow matches.  One way, used by the userspace datapath, is\nOVS_KEY_ATTR_PACKET_TYPE.  Another way, used by the kernel datapath, is\nOVS_KEY_ATTR_ETHERTYPE when used in the absence of OVS_KEY_ATTR_ETHERNET;\nwhen the latter is present, the packet is always an Ethernet packet.  The\ncode to print datapath flows wasn't paying attention to this distinction\nand always omitted eth() from the output when OVS_KEY_ATTR_ETHERNET was\nfully wildcarded, which meant that upon later re-parsing the\nOVS_KEY_ATTR_ETHERNET key was omitted, which made it look like a\nnon-Ethernet match was being described.\n\nThis commit makes odp_util_format() add eth() to the output when\nOVS_KEY_ATTR_ETHERNET is present and OVS_KEY_ATTR_PACKET_TYPE is absent,\navoiding the problem.\n\nReported-by: Amar Padmanabhan <amarpadmanabhan@fb.com>\nReported-at: https://mail.openvswitch.org/pipermail/ovs-discuss/2017-December/045817.html\nReported-by: Su Wang <suwang@vmware.com>\nVMWare-BZ: #2070488\nSigned-off-by: Ben Pfaff <blp@ovn.org>\nTested-by: Yi-Hung Wei <yihung.wei@gmail.com>\nAcked-by: Yi-Hung Wei <yihung.wei@gmail.com>","distinct":true,"url":"https://api.github.com/repos/istokes/ovs/commits/16596279409827b2e0af2420888d7024d10ab99d"}]}
{"actor":{"display_login":"istokes"}}