1. 14 2月, 2020 2 次提交
  2. 13 2月, 2020 1 次提交
  3. 12 2月, 2020 10 次提交
  4. 01 2月, 2020 3 次提交
  5. 31 1月, 2020 1 次提交
    • J
      RDMA/core: Make the entire API tree static · 8889f6fa
      Jason Gunthorpe 提交于
      Compilation of mlx5 driver without CONFIG_INFINIBAND_USER_ACCESS generates
      the following error.
      
      on x86_64:
      
       ld: drivers/infiniband/hw/mlx5/main.o: in function `mlx5_ib_handler_MLX5_IB_METHOD_VAR_OBJ_ALLOC':
       main.c:(.text+0x186d): undefined reference to `ib_uverbs_get_ucontext_file'
       ld: drivers/infiniband/hw/mlx5/main.o:(.rodata+0x2480): undefined reference to `uverbs_idr_class'
       ld: drivers/infiniband/hw/mlx5/main.o:(.rodata+0x24d8): undefined reference to `uverbs_destroy_def_handler'
      
      This is happening because some parts of the UAPI description are not
      static. This is a hold over from earlier code that relied on struct
      pointers to refer to object types, now object types are referenced by
      number. Remove the unused globals and add statics to the remaining UAPI
      description elements.
      
      Remove the redundent #ifdefs around mlx5_ib_*defs and obsolete
      mlx5_ib_get_devx_tree().
      
      The compiler now trims alot more unused code, including the above
      problematic definitions when !CONFIG_INFINIBAND_USER_ACCESS.
      
      Fixes: 7be76bef ("IB/mlx5: Introduce VAR object and its alloc/destroy methods")
      Reported-by: NRandy Dunlap <rdunlap@infradead.org>
      Acked-by: NRandy Dunlap <rdunlap@infradead.org>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      8889f6fa
  6. 30 1月, 2020 1 次提交
  7. 29 1月, 2020 2 次提交
  8. 28 1月, 2020 1 次提交
    • H
      IB/mlx4: Fix leak in id_map_find_del · ea660ad7
      Håkon Bugge 提交于
      Using CX-3 virtual functions, either from a bare-metal machine or
      pass-through from a VM, MAD packets are proxied through the PF driver.
      
      Since the VF drivers have separate name spaces for MAD Transaction Ids
      (TIDs), the PF driver has to re-map the TIDs and keep the book keeping in
      a cache.
      
      Following the RDMA Connection Manager (CM) protocol, it is clear when an
      entry has to evicted from the cache. When a DREP is sent from
      mlx4_ib_multiplex_cm_handler(), id_map_find_del() is called. Similar when
      a REJ is received by the mlx4_ib_demux_cm_handler(), id_map_find_del() is
      called.
      
      This function wipes out the TID in use from the IDR or XArray and removes
      the id_map_entry from the table.
      
      In short, it does everything except the topping of the cake, which is to
      remove the entry from the list and free it. In other words, for the REJ
      case enumerated above, one id_map_entry will be leaked.
      
      For the other case above, a DREQ has been received first. The reception of
      the DREQ will trigger queuing of a delayed work to delete the
      id_map_entry, for the case where the VM doesn't send back a DREP.
      
      In the normal case, the VM _will_ send back a DREP, and id_map_find_del()
      will be called.
      
      But this scenario introduces a secondary leak. First, when the DREQ is
      received, a delayed work is queued. The VM will then return a DREP, which
      will call id_map_find_del(). As stated above, this will free the TID used
      from the XArray or IDR. Now, there is window where that particular TID can
      be re-allocated, lets say by an outgoing REQ. This TID will later be wiped
      out by the delayed work, when the function id_map_ent_timeout() is
      called. But the id_map_entry allocated by the outgoing REQ will not be
      de-allocated, and we have a leak.
      
      Both leaks are fixed by removing the id_map_find_del() function and only
      using schedule_delayed(). Of course, a check in schedule_delayed() to see
      if the work already has been queued, has been added.
      
      Another benefit of always using the delayed version for deleting entries,
      is that we do get a TimeWait effect; a TID no longer in use, will occupy
      the XArray or IDR for CM_CLEANUP_CACHE_TIMEOUT time, without any ability
      of being re-used for that time period.
      
      Fixes: 3cf69cc8 ("IB/mlx4: Add CM paravirtualization")
      Link: https://lore.kernel.org/r/20200123155521.1212288-1-haakon.bugge@oracle.comSigned-off-by: NHåkon Bugge <haakon.bugge@oracle.com>
      Signed-off-by: NManjunath Patil <manjunath.b.patil@oracle.com>
      Reviewed-by: NRama Nichanamatlu <rama.nichanamatlu@oracle.com>
      Reviewed-by: NJack Morgenstein <jackm@dev.mellanox.co.il>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      ea660ad7
  9. 26 1月, 2020 11 次提交
  10. 21 1月, 2020 1 次提交
  11. 17 1月, 2020 7 次提交