[roll] Roll fuchsia [vm-stress-test] Re-supply after err due to resize.

Overall this allows vm-stress-test to be green more often and
purple less often.  We were seeing vm-stress-test sometimes take
a long time to exit (minutes), with the kernel output complaining
about a user pager taking too long.

If the VMO is resized to be smaller between when the pager request
is generated and when it's handled by the user pager, and the
supply_pages ends up trying to supply a page beyond the shorter end
of the VMO, we can get ZX_ERR_OUT_OF_RANGE with zero pages supplied.

However, the kernel still expects the user pager to supply the pages
up to the end of the VMO, so get the vmo size before supplying pages
and keep trying until it works or fails with an unexpected error.

Tested: vm-stress-test with VMO_VALIDATION enabled
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/591361
Original-Revision: 40908972f869386c1400a440402b1f5bcbd0b268
GitOrigin-RevId: 98370352e803bf01f32e2c45850f9511d10ba2ff
Change-Id: I1fbc57880f54e1655915675d3fe9a52e770e8d89
1 file changed
tree: 15d2ac795724da5df155182f14d30a0b205c2a3b
  1. infra/
  2. third_party/
  3. firmware
  4. flower
  5. jiri.lock
  6. minimal
  7. prebuilts
  8. README.md
  9. stem
  10. 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.