os/bluestore: Fix unittest_bluefs

Initialize data that does to disk.
It was unused and irrelevant but irritated valgrind.

Signed-off-by: Adam Kupczyk <akupczyk@ibm.com>

diff --git a/src/test/objectstore/test_bluefs.cc b/src/test/objectstore/test_bluefs.cc
index 4f77d8597ae1d571ce6b03240c5f0f0b9f82582d..260009e2002145ff61f81cfb5916a23720e52507 100644 (file)
--- a/src/test/objectstore/test_bluefs.cc
+++ b/src/test/objectstore/test_bluefs.cc
@@ -801,7 +801,7 @@ TEST(BlueFS, test_replay_growth) {
   ASSERT_EQ(0, fs.maybe_verify_layout({ BlueFS::BDEV_DB, false, false }));
   ASSERT_EQ(0, fs.mkdir("dir"));
 
-  char data[2000];
+  char data[2000] = {'x'};
   BlueFS::FileWriter *h;
   ASSERT_EQ(0, fs.open_for_write("dir", "file", &h, false));
   for (size_t i = 0; i < 10000; i++) {
@@ -989,7 +989,7 @@ TEST(BlueFS, test_update_ino1_delta_after_replay) {
   ASSERT_EQ(0, fs.maybe_verify_layout({ BlueFS::BDEV_DB, false, false }));
   ASSERT_EQ(0, fs.mkdir("dir"));
 
-  char data[2000];
+  char data[2000] = {'a'};
   BlueFS::FileWriter *h;
   ASSERT_EQ(0, fs.open_for_write("dir", "file", &h, false));
   for (size_t i = 0; i < 100; i++) {