[roll] Roll fuchsia [fshost] Correctly handle FDR for Fxblob

The `data` flag isn't set in Fxblob, so ShredDataVolume will launch a
dynamic instance of Fxfs instead of attaching to the existing instance,
which results in confusing and racy behaviour since both Fxfs instances
are sharing the same block device.

No test is added since it's rather tricky to write a test for
this (the other Fxfs instance would need to be actually doing some work
concurrently), and I intend to write an e2e test anyways.

Original-Bug: 306749272
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1045221
Original-Revision: dafd0f2e61a877f441fb6e83fdc54e3208243d6b
GitOrigin-RevId: faf3c95e6824d3b14cc0d9dbfc85d96d28ab0f7e
Change-Id: Ieeb955bd284e9df577a50d0b8692f5b608ffde77
1 file changed
tree: 27ec98d4cd6cc0781d08d6435ff062833cdfab2e
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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.