crimson/os/seastore/seastore: return future when no element error tolerated

OP_REMOVE etc ops will tolerate absent onode, we need return
ready future to chain the continuation, otherwise it will cause
a segmentation fault.

Signed-off-by: luo rixin <luorixin@huawei.com>

diff --git a/src/crimson/os/seastore/seastore.cc b/src/crimson/os/seastore/seastore.cc
index c02b00d977fb7e8a8eb8f21f7ad225f083a14fee..a6161b1f3ae8369afde370c9426065a91fafed79 100644 (file)
--- a/src/crimson/os/seastore/seastore.cc
+++ b/src/crimson/os/seastore/seastore.cc
@@ -1357,6 +1357,7 @@ SeaStore::tm_ret SeaStore::_do_transaction_step(
           op->op == Transaction::OP_OMAP_SETHEADER) {
         ceph_abort_msg("unexpected enoent error");
       }
+      return seastar::now();
     }),
     crimson::ct_error::assert_all{
       "Invalid error in SeaStore::do_transaction_step"