Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 17 3月, 2016 2 次提交
  3. 05 3月, 2016 1 次提交
  5. 03 3月, 2016 6 次提交
  7. 02 3月, 2016 2 次提交
    • M
      IB/core: Add vendor's specific data to alloc mw · b2a239df
      由 Matan Barak 提交于 
      Passing udata to the vendor's driver in order to pass data from the
user-space driver to the kernel-space driver. This data will be
used in downstream patches.
Signed-off-by: NMatan Barak <matanb@mellanox.com>
Reviewed-by: NYishai Hadas <yishaih@mellanox.com>
Signed-off-by: NDoug Ledford <dledford@redhat.com>
      b2a239df
    • H
      IB/cma: Print warning on different inner and header P_Keys · 84424a7f
      由 Haggai Eran 提交于 
      Commit 4c21b5bc ("IB/cma: Add net_dev and private data checks to RDMA
CM") added checks for incoming RDMA CM requests that they can be matched to
a netdev based on the P_Key in the BTH of the request. This behavior was
reverted in commit ab3964ad ("IB/cma: Use inner P_Key to determine
netdev"), since the mlx5 and ipath drivers didn't send the correct value
in the BTH P_Key.

Since the ipath driver was removed, and the mlx5 driver can now send GSI
packets on different P_Keys, we could revert the patch to let the rdma_cm
module look on the BTH P_Key when deciding to what netdev a packet belongs.
However, that still breaks compatibility with the older drivers.

Change the behavior to print a warning when receiving a request that has a
different BTH P_Key and inner payload P_Key. In the future, after users
have seen the warnings and upgraded their setups, remove the warning and
block these requests.
Signed-off-by: NHaggai Eran <haggaie@mellanox.com>
Signed-off-by: NDoug Ledford <dledford@redhat.com>
      84424a7f
  9. 01 3月, 2016 3 次提交
  11. 12 2月, 2016 1 次提交
  13. 04 2月, 2016 1 次提交
  15. 03 2月, 2016 1 次提交
  17. 22 1月, 2016 1 次提交
    • K
      IB/sa: Fix netlink local service GFP crash · 2deeb477
      由 Kaike Wan 提交于 
      The rdma netlink local service registers a handler to handle RESOLVE
response and another handler to handle SET_TIMEOUT request. The first
thing these handlers do is to call netlink_capable() to check the
access right of the received skb to make sure that the sender has root
access. Under normal conditions, such responses and requests will be
directly forwarded to the handlers without going through the netlink_dump
pathway (see ibnl_rcv_msg() in drivers/infiniband/core/netlink.c).
However, a user application could send a RESOLVE request (not response)
to the local service, which will fall into the netlink_dump pathway,
where a new skb will be created without initializing the control block.
This new skb will be eventually forwarded to the local service RESOLVE
response handler. Unfortunately, netlink_capable() will cause general
protection fault if the skb's control block is not initialized. This
patch will address the problem by checking the skb first.
Signed-off-by: NKaike Wan <kaike.wan@intel.com>
Reported-by: NDmitry Vyukov <dvyukov@google.com>
Signed-off-by: NDoug Ledford <dledford@redhat.com>
      2deeb477
  19. 20 1月, 2016 13 次提交
  21. 24 12月, 2015 9 次提交