Project

General

Profile

Backport #18563

jewel: leak from RGWMetaSyncShardCR::incremental_sync

Added by Nathan Cutler about 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Target version:
Release:
jewel
Crash signature (v1):
Crash signature (v2):


Related issues

Copied from rgw - Bug #18300: leak from RGWMetaSyncShardCR::incremental_sync Resolved 12/16/2016

History

#1 Updated by Nathan Cutler about 7 years ago

  • Copied from Bug #18300: leak from RGWMetaSyncShardCR::incremental_sync added

#2 Updated by Nathan Cutler about 7 years ago

  • Description updated (diff)
  • Status changed from New to In Progress
  • Assignee set to Nathan Cutler

#3 Updated by Nathan Cutler about 7 years ago

  • Description updated (diff)
  • Status changed from In Progress to Need More Info
  • Assignee deleted (Nathan Cutler)

This backport is non-trivial due to the use of boost::intrusive_ptr which is not available in jewel.

#4 Updated by Alexey Sheplyakov about 7 years ago

  • Status changed from Need More Info to In Progress

This backport is non-trivial due to the use of boost::intrusive_ptr which is not available in jewel.

A clarification: jewel has no bundled boost and uses the one provided by distros.
Those versions don't have reset(ptr, bool add_ref) method yet. The work around is simple - just use the ctor instead of reset().
See https://github.com/ceph/ceph/pull/13004/commits/b1d6c2ebee2e6216cb6aa2afaa9e32ce5e571aa9

#5 Updated by Alexey Sheplyakov about 7 years ago

  • Assignee set to Alexey Sheplyakov

#6 Updated by Nathan Cutler about 7 years ago

  • Description updated (diff)

#7 Updated by Loïc Dachary about 7 years ago

  • Status changed from In Progress to Resolved
  • Target version set to v10.2.6

Also available in: Atom PDF