1. 29 11月, 2005 1 次提交
  2. 19 11月, 2005 1 次提交
    • R
      IB/umad: make sure write()s have sufficient data · eabc7793
      Roland Dreier 提交于
      Make sure that userspace passes in enough data when sending a MAD.  We
      always copy at least sizeof (struct ib_user_mad) + IB_MGMT_RMPP_HDR
      bytes from userspace, so anything less is definitely invalid.  Also,
      if the length is less than this limit, it's possible for the second
      copy_from_user() to get a negative length and trigger a BUG().
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      eabc7793
  3. 11 11月, 2005 3 次提交
  4. 07 11月, 2005 1 次提交
  5. 04 11月, 2005 1 次提交
  6. 29 10月, 2005 2 次提交
  7. 28 10月, 2005 2 次提交
  8. 26 10月, 2005 1 次提交
    • S
      [IB] Fix MAD layer DMA mappings to avoid touching data buffer once mapped · 34816ad9
      Sean Hefty 提交于
      The MAD layer was violating the DMA API by touching data buffers used
      for sends after the DMA mapping was done.  This causes problems on
      non-cache-coherent architectures, because the device doing DMA won't
      see updates to the payload buffers that exist only in the CPU cache.
      
      Fix this by having all MAD consumers use ib_create_send_mad() to
      allocate their send buffers, and moving the DMA mapping into the MAD
      layer so it can be done just before calling send (and after any
      modifications of the send buffer by the MAD layer).
      
      Tested on a non-cache-coherent PowerPC 440SPe system.
      Signed-off-by: NSean Hefty <sean.hefty@intel.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      34816ad9
  9. 21 10月, 2005 2 次提交
  10. 20 9月, 2005 1 次提交
  11. 27 8月, 2005 3 次提交
  12. 28 7月, 2005 2 次提交
  13. 26 5月, 2005 1 次提交
  14. 17 4月, 2005 2 次提交