[roll] Roll fuchsia [kernel][vm] Untracked zero intervals

Zero intervals that do not track dirty state are inserted in
pager-backed VMOs in two scenarios.
 - Creation of unbounded VMOs: The tail of the VMO after the
   page-aligned size is an untracked zero interval.
 - Setting the stream size: The range from the page-aligned stream
   size to the end of the VMO is an untracked zero interval.

These intervals allow the kernel to not report them as dirty when
querying dirty ranges, while retaining the ability to still supply
zeroes.

Run-All-Tests: true
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1171625
Original-Revision: c7c9b136ff37d8f705362ebd5c11b619fc99c0dd
GitOrigin-RevId: 2401a54f06aa85c8ee1552bf61878ae85d6fbc0b
Change-Id: Ief63e38d09cc4c609c9be3444b98fc1364137e7d
1 file changed
tree: 1d9095f2e796b9df6d6e597d8b095b85d86df9df
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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 in one of the communication channels documented at get involved.

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.