Add support for bsdiff of file system metadata blocks

test_utils.h

 // Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CHROMEOS_PLATFORM_UPDATE_ENGINE_TEST_UTILS_H__
 #define CHROMEOS_PLATFORM_UPDATE_ENGINE_TEST_UTILS_H__
 
 #include <set>
 #include <string>
 #include <vector>
+
+#include <base/scoped_ptr.h>
 #include <gtest/gtest.h>
-#include "base/scoped_ptr.h"
+
 #include "update_engine/action.h"
 #include "update_engine/subprocess.h"
 #include "update_engine/utils.h"
 
 // These are some handy functions for unittests.
 
 namespace chromeos_update_engine {
 
 // Writes the data passed to path. The file at path will be overwritten if it
 // exists. Returns true on success, false otherwise.
@@ skipping 62 matching lines @@
   0xe8, 0x05, 0x08, 0xa1, 0x45, 0x70, 0x5b, 0x8c,
   0x39, 0x28, 0xab, 0xe9, 0x6b, 0x51, 0xd2, 0xcb,
   0x30, 0x04, 0xea, 0x7d, 0x2f, 0x6e, 0x6c, 0x3b,
   0x5f, 0x82, 0xd9, 0x5b, 0x89, 0x37, 0x65, 0x65,
   0xbe, 0x9f, 0xa3, 0x5d
 };
 
 const char* const kMountPath = "/tmp/UpdateEngineTests_mnt";
 }  // namespace {}
 
+// Creates an empty ext image.
+void CreateEmptyExtImageAtPath(const std::string& path,
+                               size_t size,
+                               int block_size);
+
 // Creates an ext image with some files in it. The paths creates are
 // returned in out_paths.
 void CreateExtImageAtPath(const std::string& path,
                           std::vector<std::string>* out_paths);
 
 // Verifies that for each path in paths, it exists in the filesystem under
 // parent. Also, verifies that no additional paths are present under parent.
 // Also tests properties of various files created by CreateExtImageAtPath().
 // Intentionally copies expected_paths.
 void VerifyAllPaths(const std::string& parent,
@@ skipping 99 matching lines @@
     }
     this->processor_->ActionComplete(this, kActionCodeSuccess);
   }
   static std::string StaticType() { return "ObjectCollectorAction"; }
   std::string Type() const { return StaticType(); }
   const T& object() const { return object_; }
  private:
   T object_;
 };
 
+class ScopedLoopMounter {
+ public:
+  explicit ScopedLoopMounter(const std::string& file_path,
+                             std::string* mnt_path,
+                             unsigned long flags);
+
+ private:
+  // These objects must be destructed in the following order:

[petkov, 2010/12/15 23:30:16]

Does C++ standard ensure the destruction order?

[thieule, 2010/12/15 23:43:39]

Yes, nonstatic members are destroyed in reverse order.

On 2010/12/15 23:30:16, petkov wrote:

+  //   ScopedFilesystemUnmounter (the file system must be unmounted first)
+  //   ScopedLoopbackDeviceReleaser (then the loop device can be deleted)
+  //   ScopedDirRemover (then the mount point can be deleted)
+  scoped_ptr<ScopedDirRemover> dir_remover_;
+  scoped_ptr<ScopedLoopbackDeviceReleaser> loop_releaser_;
+  scoped_ptr<ScopedFilesystemUnmounter> unmounter_;
+};
+
 }  // namespace chromeos_update_engine
 
 #endif  // CHROMEOS_PLATFORM_UPDATE_ENGINE_TEST_UTILS_H__