Bug #54248
BlueFS improperly tracks vselector sizes in _flush_special()
% Done:
0%
Source:
Tags:
backport_processed
Backport:
quincy
Regression:
Yes
Severity:
3 - minor
Reviewed:
Description
This problem is introduced in fine grain locking refactor.
Related issues
History
#1 Updated by Adam Kupczyk about 2 years ago
- Backport set to quincy
- Pull request ID set to 44955
#2 Updated by Adam Kupczyk about 2 years ago
- Regression changed from No to Yes
#3 Updated by Adam Kupczyk about 2 years ago
- Subject changed from BlueFS improperly tracks vselector sizes in _compact_log_async to BlueFS improperly tracks vselector sizes in _flush_special()
#4 Updated by Neha Ojha about 2 years ago
- Status changed from New to Fix Under Review
#5 Updated by Neha Ojha about 2 years ago
- Status changed from Fix Under Review to Pending Backport
#6 Updated by Backport Bot about 2 years ago
- Copied to Backport #54318: quincy: BlueFS improperly tracks vselector sizes in _flush_special() added
#7 Updated by Backport Bot over 1 year ago
- Tags set to backport_processed
#8 Updated by Igor Fedotov over 1 year ago
- Status changed from Pending Backport to Resolved