1. 09 2月, 2021 1 次提交
  2. 22 1月, 2021 2 次提交
  3. 17 1月, 2021 1 次提交
  4. 14 1月, 2021 1 次提交
  5. 08 1月, 2021 1 次提交
  6. 24 11月, 2020 1 次提交
  7. 21 11月, 2020 1 次提交
  8. 12 11月, 2020 3 次提交
    • R
      ch_ktls/cxgb4: handle partial tag alone SKBs · 21f82acb
      Rohit Maheshwari 提交于
      If TCP congestion caused a very small packets which only has some
      part fo the TAG, and that too is not till the end. HW can't handle
      such case, so falling back to sw crypto in such cases.
      
      v1->v2:
      - Marked chcr_ktls_sw_fallback() static.
      
      Fixes: dc05f3df ("chcr: Handle first or middle part of record")
      Signed-off-by: NRohit Maheshwari <rohitm@chelsio.com>
      Signed-off-by: NJakub Kicinski <kuba@kernel.org>
      21f82acb
    • R
      cxgb4/ch_ktls: creating skbs causes panic · 687823d2
      Rohit Maheshwari 提交于
      Creating SKB per tls record and freeing the original one causes
      panic. There will be race if connection reset is requested. By
      freeing original skb, refcnt will be decremented and that means,
      there is no pending record to send, and so tls_dev_del will be
      requested in control path while SKB of related connection is in
      queue.
       Better approach is to use same SKB to send one record (partial
      data) at a time. We still have to create a new SKB when partial
      last part of a record is requested.
       This fix introduces new API cxgb4_write_partial_sgl() to send
      partial part of skb. Present cxgb4_write_sgl can only provide
      feasibility to start from an offset which limits to header only
      and it can write sgls for the whole skb len. But this new API
      will help in both. It can start from any offset and can end
      writing in middle of the skb.
      
      v4->v5:
      - Removed extra changes.
      
      Fixes: 429765a1 ("chcr: handle partial end part of a record")
      Signed-off-by: NRohit Maheshwari <rohitm@chelsio.com>
      Signed-off-by: NJakub Kicinski <kuba@kernel.org>
      687823d2
    • R
      cxgb4/ch_ktls: decrypted bit is not enough · 9d2e5e9e
      Rohit Maheshwari 提交于
      If skb has retransmit data starting before start marker, e.g. ccs,
      decrypted bit won't be set for that, and if it has some data to
      encrypt, then it must be given to crypto ULD. So in place of
      decrypted, check if socket is tls offloaded. Also, unless skb has
      some data to encrypt, no need to give it for tls offload handling.
      
      v2->v3:
      - Removed ifdef.
      
      Fixes: 5a4b9fe7 ("cxgb4/chcr: complete record tx handling")
      Signed-off-by: NRohit Maheshwari <rohitm@chelsio.com>
      Signed-off-by: NJakub Kicinski <kuba@kernel.org>
      9d2e5e9e
  9. 08 11月, 2020 1 次提交
  10. 27 10月, 2020 1 次提交
  11. 15 10月, 2020 1 次提交
    • H
      cxgb4: handle 4-tuple PEDIT to NAT mode translation · 2ef813b8
      Herat Ramani 提交于
      The 4-tuple NAT offload via PEDIT always overwrites all the 4-tuple
      fields even if they had not been explicitly enabled. If any fields in
      the 4-tuple are not enabled, then the hardware overwrites the
      disabled fields with zeros, instead of ignoring them.
      
      So, add a parser that can translate the enabled 4-tuple PEDIT fields
      to one of the NAT mode combinations supported by the hardware and
      hence avoid overwriting disabled fields to 0. Any rule with
      unsupported NAT mode combination is rejected.
      Signed-off-by: NHerat Ramani <herat@chelsio.com>
      Signed-off-by: NJakub Kicinski <kuba@kernel.org>
      2ef813b8
  12. 09 10月, 2020 1 次提交
  13. 30 9月, 2020 3 次提交
  14. 18 9月, 2020 1 次提交
  15. 15 9月, 2020 1 次提交
  16. 12 9月, 2020 1 次提交
  17. 10 9月, 2020 1 次提交
  18. 06 9月, 2020 1 次提交
  19. 01 9月, 2020 1 次提交
    • P
      cxgb4: fix thermal zone device registration · 6b6382a8
      Potnuri Bharat Teja 提交于
      When multiple adapters are present in the system, pci hot-removing second
      adapter leads to the following warning as both the adapters registered
      thermal zone device with same thermal zone name/type.
      Therefore, use unique thermal zone name during thermal zone device
      initialization. Also mark thermal zone dev NULL once unregistered.
      
      [  414.370143] ------------[ cut here ]------------
      [  414.370944] sysfs group 'power' not found for kobject 'hwmon0'
      [  414.371747] WARNING: CPU: 9 PID: 2661 at fs/sysfs/group.c:281
       sysfs_remove_group+0x76/0x80
      [  414.382550] CPU: 9 PID: 2661 Comm: bash Not tainted 5.8.0-rc6+ #33
      [  414.383593] Hardware name: Supermicro X10SRA-F/X10SRA-F, BIOS 2.0a 06/23/2016
      [  414.384669] RIP: 0010:sysfs_remove_group+0x76/0x80
      [  414.385738] Code: 48 89 df 5b 5d 41 5c e9 d8 b5 ff ff 48 89 df e8 60 b0 ff ff
       eb cb 49 8b 14 24 48 8b 75 00 48 c7 c7 90 ae 13 bb e8 6a 27 d0 ff <0f> 0b 5b 5d
       41 5c c3 0f 1f 00 0f 1f 44 00 00 48 85 f6 74 31 41 54
      [  414.388404] RSP: 0018:ffffa22bc080fcb0 EFLAGS: 00010286
      [  414.389638] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
      [  414.390829] RDX: 0000000000000001 RSI: ffff8ee2de3e9510 RDI: ffff8ee2de3e9510
      [  414.392064] RBP: ffffffffbaef2ee0 R08: 0000000000000000 R09: 0000000000000000
      [  414.393224] R10: 0000000000000000 R11: 000000002b30006c R12: ffff8ee260720008
      [  414.394388] R13: ffff8ee25e0a40e8 R14: ffffa22bc080ff08 R15: ffff8ee2c3be5020
      [  414.395661] FS:  00007fd2a7171740(0000) GS:ffff8ee2de200000(0000)
       knlGS:0000000000000000
      [  414.396825] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
      [  414.398011] CR2: 00007f178ffe5020 CR3: 000000084c5cc003 CR4: 00000000003606e0
      [  414.399172] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
      [  414.400352] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
      [  414.401473] Call Trace:
      [  414.402685]  device_del+0x89/0x400
      [  414.403819]  device_unregister+0x16/0x60
      [  414.405024]  hwmon_device_unregister+0x44/0xa0
      [  414.406112]  thermal_remove_hwmon_sysfs+0x196/0x200
      [  414.407256]  thermal_zone_device_unregister+0x1b5/0x1f0
      [  414.408415]  cxgb4_thermal_remove+0x3c/0x4f [cxgb4]
      [  414.409668]  remove_one+0x212/0x290 [cxgb4]
      [  414.410875]  pci_device_remove+0x36/0xb0
      [  414.412004]  device_release_driver_internal+0xe2/0x1c0
      [  414.413276]  pci_stop_bus_device+0x64/0x90
      [  414.414433]  pci_stop_and_remove_bus_device_locked+0x16/0x30
      [  414.415609]  remove_store+0x75/0x90
      [  414.416790]  kernfs_fop_write+0x114/0x1b0
      [  414.417930]  vfs_write+0xcf/0x210
      [  414.419059]  ksys_write+0xa7/0xe0
      [  414.420120]  do_syscall_64+0x4c/0xa0
      [  414.421278]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
      [  414.422335] RIP: 0033:0x7fd2a686afd0
      [  414.423396] Code: Bad RIP value.
      [  414.424549] RSP: 002b:00007fffc1446148 EFLAGS: 00000246 ORIG_RAX:
       0000000000000001
      [  414.425638] RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007fd2a686afd0
      [  414.426830] RDX: 0000000000000002 RSI: 00007fd2a7196000 RDI: 0000000000000001
      [  414.427927] RBP: 00007fd2a7196000 R08: 000000000000000a R09: 00007fd2a7171740
      [  414.428923] R10: 00007fd2a7171740 R11: 0000000000000246 R12: 00007fd2a6b43400
      [  414.430082] R13: 0000000000000002 R14: 0000000000000001 R15: 0000000000000000
      [  414.431027] irq event stamp: 76300
      [  414.435678] ---[ end trace 13865acb4d5ab00f ]---
      
      Fixes: b1871915 ("cxgb4: Add thermal zone support")
      Signed-off-by: NPotnuri Bharat Teja <bharat@chelsio.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6b6382a8
  20. 25 8月, 2020 1 次提交
  21. 24 8月, 2020 1 次提交
  22. 22 8月, 2020 1 次提交
  23. 21 8月, 2020 1 次提交
  24. 19 8月, 2020 2 次提交
  25. 04 8月, 2020 3 次提交
  26. 24 7月, 2020 2 次提交
  27. 23 7月, 2020 1 次提交
  28. 15 7月, 2020 1 次提交
  29. 09 7月, 2020 1 次提交
  30. 01 7月, 2020 2 次提交
    • R
      cxgb4: add main VI to mirror VI config replication · 696c278f
      Rahul Lakkireddy 提交于
      When mirror VI is enabled, replicate various VI config params
      enabled on main VI to mirror VI. These include replicating MTU,
      promiscuous mode, all-multicast mode, and enabled netdev Rx
      feature offloads.
      
      v3:
      - Replace mirror VI refcount_t with normal u32 variable.
      - Add back calling cxgb4_port_mirror_start() in cxgb_open(), which
        was there in v1, but got missed in v2 during refactoring.
      
      v2:
      - Simplify the replication code by refactoring t4_set_rxmode()
        to handle mirror VI, instead of duplicating the t4_set_rxmode()
        calls in multiple places.
      Signed-off-by: NRahul Lakkireddy <rahul.lakkireddy@chelsio.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      696c278f
    • R
      cxgb4: add support for mirror Rxqs · 2b465ed0
      Rahul Lakkireddy 提交于
      When mirror VI is enabled, allocate the mirror Rxqs and setup the
      mirror VI RSS table. The mirror Rxqs are allocated/freed when
      the mirror VI is created/destroyed or when underlying port is
      brought up/down, respectively.
      
      v3:
      - Replace mirror VI refcount_t with normal u32 variable.
      
      v2:
      - Use mutex to protect all mirror VI data, instead of just
        mirror Rxqs.
      - Remove the un-needed mirror Rxq mutex.
      Signed-off-by: NRahul Lakkireddy <rahul.lakkireddy@chelsio.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2b465ed0