Project

General

Profile

Actions
Copy link

Bug #49383

closed

BlueFS reads might improperly rebuild internal buffer under an shared lock

Added by Igor Fedotov about 3 years ago. Updated about 3 years ago.

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

0%

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

Description

Both read and read_random methods in BlueFS call bufferlist::c_str() method against shared buffer under a read lock.
Which was being reported as a root cause for osd process crash. See attached Pull request for some more details

Related issues 3 (0 open — 3 closed)

Copied to bluestore - Backport #49384: pacific: BlueFS reads might improperly rebuild internal buffer under an shared lockResolvedsinguliere _Actions
Copied to bluestore - Backport #49385: nautilus: BlueFS reads might improperly rebuild internal buffer under an shared lockResolvedActions
Copied to bluestore - Backport #49386: octopus: BlueFS reads might improperly rebuild internal buffer under an shared lockResolvedsinguliere _Actions
Actions
Copy link
 #1

Updated by Igor Fedotov about 3 years ago

  • Severity changed from 3 - minor to 2 - major
Actions
Copy link
 #2

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49384: pacific: BlueFS reads might improperly rebuild internal buffer under an shared lock added
Actions
Copy link
 #3

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49385: nautilus: BlueFS reads might improperly rebuild internal buffer under an shared lock added
Actions
Copy link
 #4

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49386: octopus: BlueFS reads might improperly rebuild internal buffer under an shared lock added
Actions
Copy link
 #6

Updated by Loïc Dachary about 3 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
Copy link

Also available in: Atom PDF