[roll] Roll fuchsia [kernel][vm] Update content size on transfer

This change allows writes and appends from streams to update content
size every time bytes are transferred. Content size is now updated right
after bytes are transferred from userspace to the VMO, while the VMO
lock is still held.

Original-Fixed: 108771
Original-Fixed: 107119
Original-Bug: 82818
Original-Bug: 102657

Run-All-Tests: true
Multiply: core-stream:25
Test: core-pager-writeback
Test: core-pager
Test: core-stream

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/724650
Original-Revision: 0840c03e3f567ef4513d8a9b703f335a1bf586bc
GitOrigin-RevId: 55bdda56330749b3960b9d55705dc2c76f9379a6
Change-Id: I6418a709935af5324c2648b0a1a4228b1c35d6c2
1 file changed
tree: 0b7785dff92d8799b6ce523af1d24a876214050f
  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.