[roll] Roll fuchsia [kernel][vm] Correct old refptr upgrade comments

The refptr upgrade use to be able to fail when pages were cleaned out
of a VmCowPages in the destructor. This is no longer the case and these
couple of upgrade sites have a stale comment that could lead to
confusion.

For additional clarity a check in the evictor for a valid cow is
changed to an assert with an updated comment.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1099879
Original-Revision: 60850f6d8a2be06898e111a2f68f48d85dc23f63
GitOrigin-RevId: 31c27a84863d2f50bfc751ebb354d520f76bab13
Change-Id: I834cec602b96fde2daaa0910f3313bace7d5ae6b
1 file changed
tree: 6cf220aa1c1494ef1b21555b4e42ec1fb0c08df1
  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 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.