Project

General

Profile

Bug #1765

osd: 'call' op can return data even if op is modifying

Added by Yehuda Sadeh over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
OSD
Target version:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:

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).

History

#1 Updated by Yehuda Sadeh over 8 years ago

  • Category set to OSD

#2 Updated by Sage Weil over 8 years ago

  • translation missing: en.field_position set to 40

#3 Updated by Sage Weil over 8 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

#4 Updated by Sage Weil over 8 years ago

  • Status changed from In Progress to Resolved

commit:afc1748db52911295708e4afbe7fd7884c97dbbf

Also available in: Atom PDF