[roll] Roll fuchsia [fxfs] Flush encrypted mutations after unlock

When unlocking a volume, we should flush the encrypted mutations if
necessary to ensure we don't end up with unbounded memory.

I also took this opportunity to move the flush code into a separate
module.

Original-Bug: 92275
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/666893
Original-Revision: 8dc8aa61365891b7c063033457184ceecd3059b9
GitOrigin-RevId: d2494436ed3996ecf6c9db34a26a612fbcbd6b0b
Change-Id: Idb78cc1165046447c1fd9a875f666db145ee9046
1 file changed
tree: 71838dead0a6fb77e3a17a7ec596ff5e47ee78be
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.