[roll] Roll fuchsia [kernel][vm] Resolve all dirty requests on failure

Previously, when a userpager acknowledged a dirty request, failure cases
did not always mark the request as resolved. Given the current API
surface, this resulted in the userpager receiving an error code but no
way to inspect or detect which ranges were unresolved. The userpager was
then left with no other option but to try to resolve the requests page
by page.

This CL changes the behavior of the kernel to always mark dirty requests
as resolved, even on partial/complete failure. Operations can then
reissue dirty requests as necessary.

Original-Fixed: 108067
Original-Bug: 108197
Original-Bug: 82818
Original-Bug: 102657

Multiply: core-pager:10
Multiply: core-pager-writeback:10
Run-All-Tests: true
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/719324
Original-Revision: 79a2c8bc14b993a38767320fa4cd96854d08499b
GitOrigin-RevId: cc7418a980cbd5f575b01251bdbf2d9b4b17ca33
Change-Id: I9280bdca254c9e5242b5ec45b2e35626e5145391
1 file changed
tree: 7281c466841c496cd19ff8a0e01998d99bf48298
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.