Actions
Bug #1765
closedosd: 'call' op can return data even if op is modifying
Source:
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Not sure if it'd actually return data, but in any case the api is ambiguous. If it does return data it breaks idempotency rules. But in any case api should be less ambiguous (e.g., splitting op to two different ops, or not passing the out buffer to the method when a method is set to write).
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position set to 40
Updated by Sage Weil about 12 years ago
- Status changed from New to In Progress
- Assignee set to Sage Weil
- Target version set to v0.43
the c++ librados api now separates these operations. osd now refuses to return any result data payload if op is marked as "may write".
see wip-1765
Updated by Sage Weil about 12 years ago
- Status changed from In Progress to Resolved
commit:afc1748db52911295708e4afbe7fd7884c97dbbf
Actions