osd: refuse to write a new erasure coded object with an offset > 0

Even if the offset is properly aligned.

http://tracker.ceph.com/issues/11507 Fixes: #11507

Signed-off-by: Jianpeng Ma <jianpeng.ma@intel.com>
Signed-off-by: Loic Dachary <ldachary@redhat.com>
(cherry picked from commit a4f1256c214ee0e7ebb91ac4ea8655f5d9642dc8)

diff --git a/src/osd/ReplicatedPG.cc b/src/osd/ReplicatedPG.cc
index 92e022ef7c06582718693818023586f06408915b..975629de2c5f1f9ed1afe9cfc83fa273f501b3fc 100644 (file)
--- a/src/osd/ReplicatedPG.cc
+++ b/src/osd/ReplicatedPG.cc
@@ -3701,6 +3701,10 @@ int ReplicatedPG::do_osd_ops(OpContext *ctx, vector<OSDOp>& ops)
        }
 
        if (!obs.exists) {
+         if (pool.info.require_rollback() && op.extent.offset) {
+           result = -EOPNOTSUPP;
+           break;
+         }
          ctx->mod_desc.create();
        } else if (op.extent.offset == oi.size) {
          ctx->mod_desc.append(oi.size);