1. 21 4月, 2017 3 次提交
  2. 19 2月, 2017 1 次提交
  3. 13 1月, 2017 1 次提交
  4. 11 1月, 2017 1 次提交
    • S
      iw_cxgb4: do not send RX_DATA_ACK CPLs after close/abort · 3bcf96e0
      Steve Wise 提交于
      Function rx_data(), which handles ingress CPL_RX_DATA messages, was
      always sending an RX_DATA_ACK with the goal of updating the credits.
      However, if the RDMA connection is moved out of FPDU mode abruptly,
      then it is possible for iw_cxgb4 to process queued RX_DATA CPLs after HW
      has aborted the connection.  These CPLs should not trigger RX_DATA_ACKS.
      If they do, HW can see a READ after DELETE of the DB_LE hash entry for
      the tid and post a LE_DB HashTblMemCrcError.
      Signed-off-by: NSteve Wise <swise@opengridcomputing.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      3bcf96e0
  5. 08 10月, 2016 1 次提交
  6. 16 9月, 2016 11 次提交
  7. 04 9月, 2016 2 次提交
  8. 23 8月, 2016 2 次提交
  9. 03 8月, 2016 1 次提交
    • S
      iw_cxgb4: stop MPA_REPLY timer when disconnecting · 12eb5137
      Steve Wise 提交于
      There exists a race where the application can setup a connection
      and then disconnect it before iw_cxgb4 processes the fw4_ack
      message.  For passive side connections, the fw4_ack message is
      used to know when to stop the ep timer for MPA_REPLY messages.
      
      If the application disconnects before the fw4_ack is handled then
      c4iw_ep_disconnect() needs to clean up the timer state and stop the
      timer before restarting it for the disconnect timer.  Failure to do this
      results in a "timer already started" message and a premature stopping
      of the disconnect timer.
      
      Fixes: e4b76a2a ("RDMA/iw_cxgb4: stop_ep_timer() after MPA negotiation")
      Signed-off-by: NSteve Wise <swise@opengridcomputing.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      12eb5137
  10. 23 6月, 2016 4 次提交
  11. 14 5月, 2016 13 次提交