crimson/net: fix messenger creation

sharded data structures should only be allocated in core#0, or the
program will hang during exit.

Signed-off-by: Yingxin Cheng <yingxincheng@gmail.com>

diff --git a/src/crimson/net/Fwd.h b/src/crimson/net/Fwd.h
index 8dbb3cabbc65497255dccbde56ae9908bba24835..f47b61dc1c5fb0611b8702e1da62da76cfd166b8 100644 (file)
--- a/src/crimson/net/Fwd.h
+++ b/src/crimson/net/Fwd.h
@@ -40,14 +40,19 @@ class Messenger;
 
 template <typename T, typename... Args>
 seastar::future<T*> create_sharded(Args... args) {
-  auto sharded_obj = seastar::make_lw_shared<seastar::sharded<T>>();
-  return sharded_obj->start(args...).then([sharded_obj]() {
-      auto ret = &sharded_obj->local();
+  // seems we should only construct/stop shards on #0
+  return seastar::smp::submit_to(0, [=] {
+    auto sharded_obj = seastar::make_lw_shared<seastar::sharded<T>>();
+    return sharded_obj->start(args...).then([sharded_obj]() {
       seastar::engine().at_exit([sharded_obj]() {
           return sharded_obj->stop().finally([sharded_obj] {});
         });
-      return ret;
+      return sharded_obj.get();
     });
+  }).then([] (seastar::sharded<T> *ptr_shard) {
+    // return the pointer valid for the caller CPU
+    return &ptr_shard->local();
+  });
 }
 
 } // namespace ceph::net