[roll] Roll fuchsia [fxfs] Move crypt operations outside of flush lock during unlock

To prevent a stalled crypt service from blocking compactions during
store unlock, we move all crypt service operations (opening layers,
unwrapping keys, pre-caching keys) outside of the flush lock.

TAG=agy
CONV=920ec6fa-3a70-4cfe-a1ad-fcb91c96a37b

Original-Original-Bug: 529815538
Test: fxfs-tests
Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1689015
Original-Original-Revision: 31b1be53c2aca6758721a0b599e375193a1b0c04
GitOrigin-RevId: dbf80ade38f63a594c4a9385aa5f447b5d21e4c0
Change-Id: I1131cfa258677f82dddccefc83a2b73c0e8b846c
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1700654
Cr-Commit-Position: refs/heads/main@{#196623}
1 file changed
tree: 8769a5a8b3e8887127fe52f73a1789a183f04e10
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
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 in one of the communication channels documented at get involved.

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.