[roll] Roll fuchsia [kernel][vm] Fully initialize VMO pages

The PageQueues expect, via ASSERTs, that the initial object and
page_offset are cleared. Not initializing this has happened to work so
far due to these being zeroed at kernel boot, and always reset to zero
being the page is returned.

However, as the vm_page_t::object field is a union, other page states
that do not clear their data before returning the page can result in a
freshly allocated vm_page_t having non-zero object or page_offset
fields which, due to not being cleared, cause the asserts in the
PageQueues to spuriously fail.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1262185
Original-Revision: 2fb9003b747863e5644933a7bf93990198c42634
GitOrigin-RevId: b7ea55318720188ffcd2fb192c450dc0be043f6d
Change-Id: I3ed8ffdbb25e945c6d3b70f4a1b2e45140036dcb
1 file changed
tree: f414964d86e6b61d91c2e0d0c01026c0fcec61e5
  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.