[roll] Roll fuchsia [fvm] spot check minfs format before serving

If the fvm component is supposed to start a minfs instance on one of its
volumes, use content sniffing to spot-check if it's even remotely the
right format before we blindly try serving it.

This prevents minfs from printing a bunch of scary-looking error
messages about corruption in an otherwise normal codepath.

Original-Bug: 391891190
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1196100
Original-Revision: c2a8f31b821ae5e95fd6ab44d6d3d6c161045f8c
GitOrigin-RevId: c956e86ed5444d1b4cd55829dc9eb5da3fca5533
Change-Id: Iaffc0292857e9e4d3d67f694bc3b7417a77030b2
1 file changed
tree: a6242874aed00be187a7b617e9ee640c20eedf69
  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 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.