Project

General

Profile

Bug #40416

segfault in RGWCopyObj::verify_permission()

Added by Casey Bodley almost 5 years ago. Updated over 4 years ago.

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

0%

Source:
Q/A
Tags:
Backport:
mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

during s3tests for copy (ex. http://qa-proxy.ceph.com/teuthology/cbodley-2019-06-18_17:33:50-rgw-wip-cbodley-testing-distro-basic-smithi/4046162/teuthology.log)

2019-06-18T17:56:38.003 INFO:tasks.rgw.client.0.smithi085.stdout:*** Caught signal (Segmentation fault) **
2019-06-18T17:56:38.004 INFO:tasks.rgw.client.0.smithi085.stdout: in thread 7f9a05b1a700 thread_name:civetweb-worker
2019-06-18T17:56:38.005 INFO:tasks.rgw.client.0.smithi085.stdout: ceph version 15.0.0-1982-g40e377c (40e377c0e2ec8324b47adc843d13e39db8ee6396) octopus (dev)
2019-06-18T17:56:38.005 INFO:tasks.rgw.client.0.smithi085.stdout: 1: (()+0x12890) [0x7f9a33bf7890]
2019-06-18T17:56:38.005 INFO:tasks.rgw.client.0.smithi085.stdout: 2: (()+0x18e5a1) [0x7f9a332a05a1]
2019-06-18T17:56:38.005 INFO:tasks.rgw.client.0.smithi085.stdout: 3: (RGWCopyObj::verify_permission()+0x7c8) [0x5618e64df018]
2019-06-18T17:56:38.006 INFO:tasks.rgw.client.0.smithi085.stdout: 4: (rgw_process_authenticated(RGWHandler_REST*, RGWOp*&, RGWRequest*, req_state*, bool)+0xcee) [0x5618e621eebe]
2019-06-18T17:56:38.006 INFO:tasks.rgw.client.0.smithi085.stdout: 5: (process_request(RGWRados*, RGWREST*, RGWRequest*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, rgw::auth::StrategyRegistry const&, RGWRestfulIO*, OpsLogSocket*, optional_yield, rgw::dmclock::Scheduler*, int*)+0x2ff4) [0x5618e62234c4]
2019-06-18T17:56:38.006 INFO:tasks.rgw.client.0.smithi085.stdout: 6: (RGWCivetWebFrontend::process(mg_connection*)+0x36e) [0x5618e616144e]
2019-06-18T17:56:38.006 INFO:tasks.rgw.client.0.smithi085.stdout: 7: (()+0x37ebe2) [0x5618e61e6be2]
2019-06-18T17:56:38.006 INFO:tasks.rgw.client.0.smithi085.stdout: 8: (()+0x38086f) [0x5618e61e886f]
2019-06-18T17:56:38.006 INFO:tasks.rgw.client.0.smithi085.stdout: 9: (()+0x380d28) [0x5618e61e8d28]
2019-06-18T17:56:38.006 INFO:tasks.rgw.client.0.smithi085.stdout: 10: (()+0x76db) [0x7f9a33bec6db]
2019-06-18T17:56:38.007 INFO:tasks.rgw.client.0.smithi085.stdout: 11: (clone()+0x3f) [0x7f9a3323388f]
2019-06-18T17:56:38.007 INFO:tasks.rgw.client.0.smithi085.stdout:2019-06-18T17:56:38.004+0000 7f9a05b1a700 -1 *** Caught signal (Segmentation fault) **
2019-06-18T17:56:38.008 INFO:tasks.rgw.client.0.smithi085.stdout: in thread 7f9a05b1a700 thread_name:civetweb-worker

Related issues

Copied to rgw - Backport #40847: mimic: segfault in RGWCopyObj::verify_permission() Resolved
Copied to rgw - Backport #40848: nautilus: segfault in RGWCopyObj::verify_permission() Resolved

History

#1 Updated by Casey Bodley almost 5 years ago

  • Priority changed from Normal to High

#2 Updated by Casey Bodley almost 5 years ago

  • Status changed from New to Triaged
  • Assignee set to Casey Bodley

the failures appear to be correlated with ubuntu 18.04. setting up a bionic vm to try reproducing

#3 Updated by Casey Bodley almost 5 years ago

does not reproduce with a vstart cluster on bionic

#4 Updated by Casey Bodley over 4 years ago

  • Status changed from Triaged to 12
  • Assignee changed from Casey Bodley to Adam Emerson

#5 Updated by Adam Emerson over 4 years ago

  • Status changed from 12 to Fix Under Review

#6 Updated by Casey Bodley over 4 years ago

  • Backport set to mimic nautilus

#7 Updated by Casey Bodley over 4 years ago

  • Status changed from Fix Under Review to Pending Backport

#8 Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #40847: mimic: segfault in RGWCopyObj::verify_permission() added

#9 Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #40848: nautilus: segfault in RGWCopyObj::verify_permission() added

#10 Updated by Nathan Cutler over 4 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".

Also available in: Atom PDF