[roll] Roll fuchsia [kernel][vm] Simplify range change reasoning

Moves the range change update in ZeroPagesLocked out of the if into
the main body of the method. Guarding the range change by the if is
correct, since if can_decommit_zero_pages is false we will not be able
to remove any pages or otherwise modify the page list in a way that
would require a range change update, but this correctness is subtle.

Given that performing a zero range on a contiguous vmo is a very
uncommon operation, performing an additional unmap in this case is
worth the additional clarity.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1213765
Original-Revision: ea22eb6d45454e45e8106044e4a91d5fed73bd41
GitOrigin-RevId: 939739f7efad1a8769403545304d1da1c65a272a
Change-Id: Iae16c9607877d9fdf52291cf294638bc2399dcde
1 file changed
tree: 2089731bf71389d75a6afec5addef09f6578bbbe
  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.