[roll] Roll fuchsia [kernel][bti] Fix an assert trigged by a failed zx_bti_pin. When the newly refactored Stub IOMMU implementation encountered invalid arguments during a zx_bti_pin operation, it was internally attempting to release its `pinned_vmo_` member twice, triggering an assert. Note, this was more of an annoyance than an actual error as calling `.reset()` on a PinnedVmObject is an idempotent operation, but the ASSERT needs to be cleaned up regardless. Also, add a new core test which attempts to exercise all of the different ways in a request to pin might be considered to have INVALID_ARGS. Original-Fixed: 507926838 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1599712 Original-Revision: f36e4c2507176f78278927aa43cdc7f88a695df9 GitOrigin-RevId: 4e8f3c8498d31c36c3db61474af7f6399ff46a5a Change-Id: Id07204a88926ccfc4296577a0a4826c52b9b94f5
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.