1. 19 6月, 2019 2 次提交
  2. 18 6月, 2019 1 次提交
  3. 12 6月, 2019 2 次提交
  4. 11 6月, 2019 3 次提交
  5. 22 5月, 2019 2 次提交
  6. 07 5月, 2019 4 次提交
  7. 03 5月, 2019 4 次提交
  8. 02 5月, 2019 1 次提交
  9. 25 4月, 2019 1 次提交
  10. 24 4月, 2019 3 次提交
  11. 09 4月, 2019 5 次提交
  12. 02 4月, 2019 4 次提交
  13. 30 3月, 2019 1 次提交
  14. 29 3月, 2019 3 次提交
  15. 26 3月, 2019 1 次提交
  16. 23 2月, 2019 1 次提交
  17. 20 2月, 2019 2 次提交
    • S
      RDMA/core: Add RDMA_NLDEV_CMD_NEWLINK/DELLINK support · 3856ec4b
      Steve Wise 提交于
      Add support for new LINK messages to allow adding and deleting rdma
      interfaces.  This will be used initially for soft rdma drivers which
      instantiate device instances dynamically by the admin specifying a netdev
      device to use.  The rdma_rxe module will be the first user of these
      messages.
      
      The design is modeled after RTNL_NEWLINK/DELLINK: rdma drivers register
      with the rdma core if they provide link add/delete functions.  Each driver
      registers with a unique "type" string, that is used to dispatch messages
      coming from user space.  A new RDMA_NLDEV_ATTR is defined for the "type"
      string.  User mode will pass 3 attributes in a NEWLINK message:
      RDMA_NLDEV_ATTR_DEV_NAME for the desired rdma device name to be created,
      RDMA_NLDEV_ATTR_LINK_TYPE for the "type" of link being added, and
      RDMA_NLDEV_ATTR_NDEV_NAME for the net_device interface to use for this
      link.  The DELLINK message will contain the RDMA_NLDEV_ATTR_DEV_INDEX of
      the device to delete.
      Signed-off-by: NSteve Wise <swise@opengridcomputing.com>
      Reviewed-by: NLeon Romanovsky <leonro@mellanox.com>
      Reviewed-by: NMichael J. Ruhl <michael.j.ruhl@intel.com>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      3856ec4b
    • J
      RDMA/rxe: Close a race after ib_register_device · ca22354b
      Jason Gunthorpe 提交于
      Since rxe allows unregistration from other threads the rxe pointer can
      become invalid any moment after ib_register_driver returns. This could
      cause a user triggered use after free.
      
      Add another driver callback to be called right after the device becomes
      registered to complete any device setup required post-registration.  This
      callback has enough core locking to prevent the device from becoming
      unregistered.
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      ca22354b