[roll] Roll fuchsia [netstack] Avoid leaking pprof VMO

(*component.fileState).GetBackingMemory() expects not to be responsible
for closing the VMO handle returned from (*component.File).GetVMO().
This is problematic because the existing netstack pprofFile
implementation allocates a new VMO when GetVMO is called, and nothing
was closing the original handle to that VMO.

To fix this, we move GetVMO to the component.Reader interface so that
(*component.Reader).Close() can also close the Reader's VMO handle if
it is backed by a VMO.

Original-Bug: 109616
Test: pprof-gotests
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/735005
Original-Revision: e77f0783e89fcbfed969d5888eb7b3f34df5bdae
GitOrigin-RevId: c22d98cb0daf91f0aadef96c8d4224bf844fc20f
Change-Id: I0a61c109bb10eb5327b069271af034fb8fd39c5d
1 file changed
tree: b43d5a5c29d7b0f4d64ffa113a256af2b509e0bd
  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.