1. 01 9月, 2011 1 次提交
  2. 27 7月, 2011 1 次提交
  3. 14 6月, 2011 1 次提交
  4. 08 6月, 2011 1 次提交
  5. 25 5月, 2011 1 次提交
  6. 20 5月, 2011 2 次提交
  7. 04 5月, 2011 1 次提交
  8. 07 4月, 2011 1 次提交
  9. 31 3月, 2011 1 次提交
  10. 30 3月, 2011 1 次提交
    • S
      libceph: fix null dereference when unregistering linger requests · fbdb9190
      Sage Weil 提交于
      We should only clear r_osd if we are neither registered as a linger or a
      regular request.  We may unregister as a linger while still registered as
      a regular request (e.g., in reset_osd).  Incorrectly clearing r_osd there
      leads to a null pointer dereference in __send_request.
      
      Also simplify the parallel check in __unregister_request() where we just
      removed r_osd_item and know it's empty.
      Signed-off-by: NSage Weil <sage@newdream.net>
      fbdb9190
  11. 29 3月, 2011 1 次提交
  12. 27 3月, 2011 1 次提交
  13. 23 3月, 2011 1 次提交
  14. 22 3月, 2011 1 次提交
    • S
      libceph: fix osd request queuing on osdmap updates · 6f6c7006
      Sage Weil 提交于
      If we send a request to osd A, and the request's pg remaps to osd B and
      then back to A in quick succession, we need to resend the request to A. The
      old code was only calling kick_requests after processing all incremental
      maps in a message, so it was very possible to not resend a request that
      needed to be resent.  This would make the osd eventually time out (at least
      with the current default of osd timeouts enabled).
      
      The correct approach is to scan requests on every map incremental.  This
      patch refactors the kick code in a few ways:
       - all requests are either on req_lru (in flight), req_unsent (ready to
         send), or req_notarget (currently map to no up osd)
       - mapping always done by map_request (previous map_osds)
       - if the mapping changes, we requeue.  requests are resent only after all
         map incrementals are processed.
       - some osd reset code is moved out of kick_requests into a separate
         function
       - the "kick this osd" functionality is moved to kick_osd_requests, as it
         is unrelated to scanning for request->pg->osd mapping changes
      Signed-off-by: NSage Weil <sage@newdream.net>
      6f6c7006
  15. 10 11月, 2010 2 次提交
    • S
      ceph: explicitly specify page alignment in network messages · c5c6b19d
      Sage Weil 提交于
      The alignment used for reading data into or out of pages used to be taken
      from the data_off field in the message header.  This only worked as long
      as the page alignment matched the object offset, breaking direct io to
      non-page aligned offsets.
      
      Instead, explicitly specify the page alignment next to the page vector
      in the ceph_msg struct, and use that instead of the message header (which
      probably shouldn't be trusted).  The alloc_msg callback is responsible for
      filling in this field properly when it sets up the page vector.
      Signed-off-by: NSage Weil <sage@newdream.net>
      c5c6b19d
    • S
      ceph: make page alignment explicit in osd interface · b7495fc2
      Sage Weil 提交于
      We used to infer alignment of IOs within a page based on the file offset,
      which assumed they matched.  This broke with direct IO that was not aligned
      to pages (e.g., 512-byte aligned IO).  We were also trusting the alignment
      specified in the OSD reply, which could have been adjusted by the server.
      
      Explicitly specify the page alignment when setting up OSD IO requests.
      Signed-off-by: NSage Weil <sage@newdream.net>
      b7495fc2
  16. 21 10月, 2010 4 次提交
  17. 07 10月, 2010 1 次提交
  18. 23 8月, 2010 1 次提交
  19. 04 8月, 2010 1 次提交
  20. 02 8月, 2010 1 次提交
  21. 28 7月, 2010 1 次提交
  22. 14 6月, 2010 1 次提交
  23. 30 5月, 2010 1 次提交
  24. 22 5月, 2010 1 次提交
  25. 18 5月, 2010 8 次提交
  26. 12 5月, 2010 2 次提交
  27. 23 3月, 2010 1 次提交
    • S
      ceph: avoid reopening osd connections when address hasn't changed · 87b315a5
      Sage Weil 提交于
      We get a fault callback on _every_ tcp connection fault.  Normally, we
      want to reopen the connection when that happens.  If the address we have
      is bad, however, and connection attempts always result in a connection
      refused or similar error, explicitly closing and reopening the msgr
      connection just prevents the messenger's backoff logic from kicking in.
      The result can be a console full of
      
      [ 3974.417106] ceph: osd11 10.3.14.138:6800 connection failed
      [ 3974.423295] ceph: osd11 10.3.14.138:6800 connection failed
      [ 3974.429709] ceph: osd11 10.3.14.138:6800 connection failed
      
      Instead, if we get a fault, and have outstanding requests, but the osd
      address hasn't changed and the connection never successfully connected in
      the first place, do nothing to the osd connection.  The messenger layer
      will back off and retry periodically, because we never connected and thus
      the lossy bit is not set.
      
      Instead, touch each request's r_stamp so that handle_timeout can tell the
      request is still alive and kicking.
      Signed-off-by: NSage Weil <sage@newdream.net>
      87b315a5