1. 06 9月, 2009 9 次提交
  2. 23 6月, 2009 2 次提交
  3. 16 5月, 2009 1 次提交
  4. 28 4月, 2009 12 次提交
  5. 22 4月, 2009 2 次提交
  6. 21 4月, 2009 2 次提交
  7. 09 4月, 2009 6 次提交
  8. 07 4月, 2009 2 次提交
  9. 27 3月, 2009 1 次提交
  10. 22 3月, 2009 1 次提交
  11. 13 3月, 2009 1 次提交
    • F
      RDMA/nes: Don't allow userspace QPs to use STag zero · c12e56ef
      Faisal Latif 提交于
      STag zero is a special STag that allows consumers to access any bus
      address without registering memory.  The nes driver unfortunately
      allows STag zero to be used even with QPs created by unprivileged
      userspace consumers, which means that any process with direct verbs
      access to the nes device can read and write any memory accessible to
      the underlying PCI device (usually any memory in the system).  Such
      access is usually given for cluster software such as MPI to use, so
      this is a local privilege escalation bug on most systems running this
      driver.
      
      The driver was using STag zero to receive the last streaming mode
      data; to allow STag zero to be disabled for unprivileged QPs, the
      driver now registers a special MR for this data.
      
      Cc: <stable@kernel.org>
      Signed-off-by: NFaisal Latif <faisal.latif@intel.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      c12e56ef
  12. 07 3月, 2009 1 次提交
    • F
      RDMA/nes: Handle MPA Reject message properly · 9d5ab133
      Faisal Latif 提交于
      While doing testing, there are failures as MPA Reject call is not
      handled.  To handle MPA Reject call, following changes are done:
      
      *Handle inbound/outbound MPA Reject response message.
      	When nes_reject() is called for pending MPA request reply,
      	send the MPA Reject message to its peer (active
      	side)cm_node. The peer cm_node (active side) will indicate
      	Reject message event for the pending Connect Request.
      
      *Handle MPA Reject response message for loopback connections and listener.
      	When MPA Request is rejected, check if it is a loopback
      	connection and if it is then it will send Reject message event
      	to its peer loopback node. Also when destroying listener,
      	check if the cm_nodes for that listener are loopback or not.
      
      *Add gracefull connection close with the MPA Reject response message.
      	Send gracefull close (FIN, FIN ACK..) to terminate the cm_nodes.
      
      *Some code re-org while making the above changes.
      	Removed recv_list and recv_list_lock from the cm_node
      	structure as there can be only one receive close entry on the
      	timer. Also implemented handle_recv_entry() as receive close
      	entry is processed from both nes_rem_ref_cm_node() as well as
      	nes_cm_timer_tick().
      Signed-off-by: NFaisal Latif <faisal.latif@intel.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      9d5ab133