copy without fsync for boot value files to reduce boot overhead.

Context: on seahawk build, when copying without explicit fsync, storage files are not properly copied eventually. It showed up on /metadata as 0 sized files. This is unexpected and only happening on seahawk devices. In theory kernel should eventually flushed copied file data from kernel buffer to filesystem. But it does not in the case of seahawk. To fix the issue, we added explicit fsync after file copy. This however added boot performance cost.

Here in this cl, we tested out copying only persist storage files with fsync. Aconfigd only copy these files when there is a system/mainline update. A normal reboot would not trigger these heavy copies. Thus reducing the normal reboot cost.

Tested out in a seahwak device, the storage files are properly populated.

Bug:b/400299282

Change-Id: Ie71eefea69ef20ab172fe83dd654622b24cb9fcb
2 files changed
tree: 968a1cc2e22a3a928e84a3904e8b380814a378ea
  1. aconfigd/
  2. aflags/
  3. apex/
  4. framework/
  5. service/
  6. OWNERS
  7. TEST_MAPPING