crimson/osd/ops_executor: calculation of clone_overlap shouldn't consider

snap contexts

Fixes: https://tracker.ceph.com/issues/65832
Signed-off-by: Xuehan Xu <xuxuehan@qianxin.com>
(cherry picked from commit 213ae3f42cbb478b503212d704161b16e90cf878)

diff --git a/src/crimson/osd/ops_executer.cc b/src/crimson/osd/ops_executer.cc
index 10020e9adf8a1e32f0c37f9a4c7891f3a2828d63..45ecd2a1404712b5d910a26e8d0c39fc6cb51ee1 100644 (file)
--- a/src/crimson/osd/ops_executer.cc
+++ b/src/crimson/osd/ops_executer.cc
@@ -980,7 +980,6 @@ void OpsExecuter::update_clone_overlap() {
       &cloning_ctx->new_snapset.clone_overlap.rbegin()->second;
   } else if (op_info.may_write() 
     && obc->obs.exists 
-    && !snapc.snaps.empty() 
     && !obc->ssc->snapset.clones.empty()) {
     newest_overlap =
       &obc->ssc->snapset.clone_overlap.rbegin()->second;