[roll] Roll fuchsia [kernel][vm] Do not dirty forked zero page on commit

When a zero page marker is replaced with a forked zero page in a
pager-backed VMO, only mark it dirty if we were looking up the page with
mark_dirty set to DirtyAllPagesOnWrite. This ensures we do not dirty
forked zero pages during a commit, which passes the VMM_PF_FLAG_WRITE so
that it can fork pages if required, but does not indicate
DirtyAllPagesOnWrite.

Test: core-pager-writeback
Original-Bug: 63989
Run-All-Tests: true
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/711243
Original-Revision: 2a44828d2bda6d8bf76b69e412433a1423e1e1be
GitOrigin-RevId: 8020a53ebee5d4c5185d3f83a7cb9b787028cdec
Change-Id: I405b2a398423fa3bc9ebc26067e69aa8c967416d
1 file changed
tree: 7950676a665780e12f4cf209d104e93ce76acba6
  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.