1. 26 10月, 2011 2 次提交
  2. 17 9月, 2011 1 次提交
    • S
      libceph: fix linger request requeuing · 935b639a
      Sage Weil 提交于
      The r_req_lru_item list node moves between several lists, and that cycle
      is not directly related (and does not begin) with __register_request().
      Initialize it in the request constructor, not __register_request(). This
      fixes later badness (below) when OSDs restart underneath an rbd mount.
      
      Crashes we've seen due to this include:
      
      [  213.974288] kernel BUG at net/ceph/messenger.c:2193!
      
      and
      
      [  144.035274] BUG: unable to handle kernel NULL pointer dereference at 0000000000000048
      [  144.035278] IP: [<ffffffffa036c053>] con_work+0x1463/0x2ce0 [libceph]
      Signed-off-by: NSage Weil <sage@newdream.net>
      935b639a
  3. 01 9月, 2011 1 次提交
  4. 27 7月, 2011 1 次提交
  5. 14 6月, 2011 1 次提交
  6. 08 6月, 2011 1 次提交
  7. 25 5月, 2011 1 次提交
  8. 20 5月, 2011 2 次提交
  9. 04 5月, 2011 1 次提交
  10. 07 4月, 2011 1 次提交
  11. 31 3月, 2011 1 次提交
  12. 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
  13. 29 3月, 2011 1 次提交
  14. 27 3月, 2011 1 次提交
  15. 23 3月, 2011 1 次提交
  16. 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
  17. 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
  18. 21 10月, 2010 4 次提交
  19. 07 10月, 2010 1 次提交
  20. 23 8月, 2010 1 次提交
  21. 04 8月, 2010 1 次提交
  22. 02 8月, 2010 1 次提交
  23. 28 7月, 2010 1 次提交
  24. 14 6月, 2010 1 次提交
  25. 30 5月, 2010 1 次提交
  26. 22 5月, 2010 1 次提交
  27. 18 5月, 2010 8 次提交