[roll] Roll fuchsia [kernel][vm] Fix commit and resize race

If a commit is blocked on a page request and a resize invalidates the
range being waited on, the commit loop should not retry with a now
invalid range when unblocked. This used to work correctly until
fxr/693384 refactored the commit path and failed to bubble up the
termination condition from a lambda to the outer control loop.

The added test fails a range check debug assert without this fix.

Test: core-pager-writeback
Original-Bug: 105012
Original-Bug: 63989
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/703346
Original-Revision: dfaa5870ec54c66825902e7affb9a12ee7840949
GitOrigin-RevId: 792d3cc1e53910602c45c4b4aeb7672c51ab8345
Change-Id: I8030e991a51888a47199df047ba77adafe53c091
1 file changed
tree: a30c382670ae307eb1e4d607f422ad5170cfef26
  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
  12. 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.