[roll] Roll fuchsia [storage] Mark BlockClient::attach_vmo unsafe
This change marks the `BlockClient::attach_vmo` trait method and its
implementations as `unsafe`. The caller must guarantee that the VMO is
only attached once to avoid potential memory corruption if the
connection is terminated while I/O is in progress.
All call sites in FVM, GPT, Fxfs (tests), `storage_device`,
`block_client` cache, and `recovery` installer have been wrapped in
`unsafe` blocks with safety documentation.
Original-Original-Bug: 517452598
Test: block-client-tests, fvm-rust-tests, gpt-component-tests,
block_server_integration, fxfs-tests
TAG=agy
CONV=8c74f469-8fb5-4972-a298-8f22a1e5e003
Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1688254
Original-Original-Revision: 079583bb1b677d1cc25dcceeefb31f246f9d75ed
GitOrigin-RevId: 1a3ea43f1d91030dbb66f4567cff0d9143e0aa1b
Change-Id: Ib7c0f4ac4d238384ffe8f20338f83caa576454a4
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1692157
Cr-Commit-Position: refs/heads/main@{#196088}
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.