[roll] Roll fuchsia [virtualization] Limit the number of in-flight requests to block devices

When a guest performs large numbers of read/writes, the virtio-block
device can currently send an unbounded number of requests to the
underlying file, exceeding Zircon's channel capacity. This leads to
a policy violation and the virtio-block process crashing.

This CL adds a RequestQueue class, limiting the number of in-flight
requests. Any request issued by the RawBlockDispatcher beyond the max
in-flight number will not be started until some existing requests
finish.

Original-Bug: 12536

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/611109
Original-Revision: e63b431fd6f1bb0dd15141c29dfc4d5a860c1a97
GitOrigin-RevId: bcf852427e8fdb46940d666885aad581e0eab0bd
Change-Id: I3b7062ecc42008182bdfe2b41c192851945b5c82
1 file changed
tree: 5aea4863cb4d3824c5714a2cb195f10090d839f1
  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
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.