1. 06 5月, 2019 1 次提交
  2. 17 4月, 2019 1 次提交
  3. 16 4月, 2019 6 次提交
  4. 23 3月, 2019 2 次提交
  5. 13 2月, 2019 1 次提交
  6. 07 2月, 2019 2 次提交
  7. 18 12月, 2018 1 次提交
    • J
      nfp: flower: fix cb_ident duplicate in indirect block register · b12c97d4
      John Hurley 提交于
      Previously the identifier used for indirect block callback registry and
      for block rule cb registry (when done via indirect blocks) was the pointer
      to the netdev we were interested in receiving updates on. This worked fine
      if a single app existed that registered one callback per netdev of
      interest. However, if multiple cards are in place and, in turn, multiple
      apps, then each app may register the same callback with the same
      identifier to both the netdev's indirect block cb list and to a block's cb
      list. This can lead to EEXIST errors and/or incorrect cb deletions.
      
      Prevent this conflict by using the app pointer as the identifier for
      netdev indirect block cb registry, allowing each app to register a unique
      callback per netdev. For block cb registry, the same app may register
      multiple cbs to the same block if using TC shared blocks. Instead of the
      app, use the pointer to the allocated cb_priv data as the identifier here.
      This means that there can be a unique block callback for each app/netdev
      combo.
      
      Fixes: 3166dd07 ("nfp: flower: offload tunnel decap rules via indirect TC blocks")
      Reported-by: NEdward Cree <ecree@solarflare.com>
      Signed-off-by: NJohn Hurley <john.hurley@netronome.com>
      Reviewed-by: NJakub Kicinski <jakub.kicinski@netronome.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b12c97d4
  8. 11 12月, 2018 1 次提交
  9. 01 12月, 2018 2 次提交
  10. 12 11月, 2018 4 次提交
  11. 12 10月, 2018 1 次提交
  12. 11 10月, 2018 2 次提交
  13. 13 9月, 2018 1 次提交
  14. 08 8月, 2018 2 次提交
  15. 23 7月, 2018 1 次提交
  16. 27 6月, 2018 2 次提交
  17. 26 6月, 2018 1 次提交
  18. 25 6月, 2018 1 次提交
  19. 25 5月, 2018 1 次提交
  20. 26 4月, 2018 2 次提交
  21. 27 3月, 2018 1 次提交
  22. 17 2月, 2018 1 次提交
  23. 08 2月, 2018 1 次提交
  24. 26 1月, 2018 1 次提交
  25. 20 12月, 2017 1 次提交