1. 23 2月, 2013 1 次提交
    • B
      openvswitch: Allow OVS_USERSPACE_ATTR_USERDATA to be variable length. · 4490108b
      Ben Pfaff 提交于
      Until now, the optional OVS_USERSPACE_ATTR_USERDATA attribute had to be
      exactly 64 bits long, if it was present.  However, 64 bits is not enough
      space to associate as much information with a flow as would be convenient
      for some userspace features now under development.  This commit generalizes
      the attribute, allowing it to be any length.
      
      This generalization is backward-compatible: if userspace only uses 64-bit
      attributes, then it will not see any change in behavior.
      
      CC: Romain Lenglet <rlenglet@vmware.com>
      Signed-off-by: NBen Pfaff <blp@nicira.com>
      Signed-off-by: NJesse Gross <jesse@nicira.com>
      4490108b
  2. 10 1月, 2013 1 次提交
  3. 05 12月, 2012 2 次提交
  4. 29 11月, 2012 1 次提交
  5. 27 11月, 2012 1 次提交
  6. 17 11月, 2012 1 次提交
  7. 14 11月, 2012 1 次提交
  8. 03 11月, 2012 1 次提交
  9. 31 10月, 2012 2 次提交
  10. 19 9月, 2012 1 次提交
  11. 11 9月, 2012 1 次提交
  12. 04 9月, 2012 2 次提交
  13. 03 9月, 2012 1 次提交
  14. 01 9月, 2012 1 次提交
  15. 23 8月, 2012 1 次提交
  16. 07 8月, 2012 1 次提交
    • J
      openvswitch: Relax set header validation. · 4185392d
      Jesse Gross 提交于
      When installing a flow with an action to set a particular field we
      need to validate that the packets that are part of the flow actually
      contain that header.  With IP we use zeroed addresses and with TCP/UDP
      the check is for zeroed ports.  This check is overly broad and can catch
      packets like DHCP requests that have a zero source address in a
      legitimate header.  This changes the check to look for a zeroed protocol
      number for IP or for both ports be zero for TCP/UDP before considering
      the header to not exist.
      Reported-by: NEthan Jackson <ethan@nicira.com>
      Signed-off-by: NJesse Gross <jesse@nicira.com>
      4185392d
  17. 28 7月, 2012 1 次提交
  18. 23 7月, 2012 1 次提交
  19. 21 7月, 2012 2 次提交
  20. 26 5月, 2012 1 次提交
    • J
      openvswitch: Reset upper layer protocol info on internal devices. · 7fe99e2d
      Jesse Gross 提交于
      It's possible that packets that are sent on internal devices (from
      the OVS perspective) have already traversed the local IP stack.
      After they go through the internal device, they will again travel
      through the IP stack which may get confused by the presence of
      existing information in the skb. The problem can be observed
      when switching between namespaces. This clears out that information
      to avoid problems but deliberately leaves other metadata alone.
      This is to provide maximum flexibility in chaining together OVS
      and other Linux components.
      Signed-off-by: NJesse Gross <jesse@nicira.com>
      7fe99e2d
  21. 16 5月, 2012 1 次提交
  22. 14 5月, 2012 1 次提交
  23. 08 5月, 2012 1 次提交
  24. 04 5月, 2012 2 次提交
  25. 16 4月, 2012 1 次提交
  26. 10 4月, 2012 1 次提交
  27. 03 4月, 2012 2 次提交
  28. 02 4月, 2012 1 次提交
  29. 29 3月, 2012 1 次提交
  30. 08 3月, 2012 1 次提交
  31. 07 3月, 2012 1 次提交
  32. 16 2月, 2012 1 次提交
  33. 18 1月, 2012 1 次提交
  34. 17 1月, 2012 1 次提交