Project

General

Profile

Actions

Bug #49321

closed

Segmentation fault on GC with big value of rgw_gc_max_objs

Added by Rafal Wadolowski about 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

100%

Source:
Tags:
gc
Backport:
pacific octopus nautilus
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When you set rgw_gc_max_objs higher than 65521, then you get following SEGV

     0> 2021-02-17 01:20:43.185 7f95d30b4700 -1 *** Caught signal (Segmentation fault) **
 in thread 7f95d30b4700 thread_name:rgw_gc

 ceph version 14.2.11-cf1 (13198c41444d21141888d6706531517d52b67b61) nautilus (stable)
 1: (()+0x11390) [0x7f95e7b4f390]
 2: (()+0x9f8c0) [0x7f95e750a8c0]
 3: (()+0x594ac) [0x7f95f26de4ac]
 4: (librados::v14_2_0::IoCtx::aio_operate(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, librados::v14_2_0::AioCompletion*, librados::v14_2_0::ObjectWriteOperation*)+0x4b) [0x7f95f26e05eb]
 5: (RGWRados::gc_aio_operate(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, librados::v14_2_0::ObjectWriteOperation*, librados::v14_2_0::AioCompletion**)+0x3b) [0x9d3f6b]
 6: (RGWGC::remove(int, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&, librados::v14_2_0::AioCompletion**)+0x78) [0xb3b
058]
 7: (RGWGCIOManager::flush_remove_tags(int, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&)+0xdc) [0xb4053c]
 8: (RGWGC::process(bool)+0x555) [0xb3e6a5]
 9: (RGWGC::GCWorker::entry()+0x272) [0xb3ed52]
 10: (()+0x76ba) [0x7f95e7b456ba]
 11: (clone()+0x6d) [0x7f95e75724dd]
 NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this.

Related issues 3 (0 open3 closed)

Copied to rgw - Backport #49743: pacific: Segmentation fault on GC with big value of rgw_gc_max_objsResolvedsinguliere _Actions
Copied to rgw - Backport #49744: nautilus: Segmentation fault on GC with big value of rgw_gc_max_objsResolvedNathan CutlerActions
Copied to rgw - Backport #49745: octopus: Segmentation fault on GC with big value of rgw_gc_max_objsResolvedsinguliere _Actions
Actions #2

Updated by Casey Bodley about 3 years ago

  • Status changed from New to Fix Under Review
  • Tags set to gc
Actions #3

Updated by Casey Bodley about 3 years ago

  • Pull request ID set to 39515
Actions #4

Updated by Casey Bodley about 3 years ago

  • Backport set to pacific octopus nautilus
Actions #5

Updated by Casey Bodley about 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #6

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49743: pacific: Segmentation fault on GC with big value of rgw_gc_max_objs added
Actions #7

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49744: nautilus: Segmentation fault on GC with big value of rgw_gc_max_objs added
Actions #8

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49745: octopus: Segmentation fault on GC with big value of rgw_gc_max_objs added
Actions #9

Updated by Loïc Dachary over 2 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF