[roll] Roll fuchsia [utest] aarch32 max_load_address checking This change fixes two oversights in max_load_address usage: For MapSharedStorage() there is an off-by-one which would leave the trailing byte of a mapping at the max_load_address inaccessible to the restricted mode environment, 0x100000000 versus 0xffffffff. For restricted blob allocation, the current search only ensures that the starting address is under the limit. This change adds checking to ensure the entire blob is able to fit under the max_load_address. Original-Bug: 389733983 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1186537 Original-Revision: d9b0f283ec7cd0025b66fc8072b75e00c40dbd52 GitOrigin-RevId: a24c83a8f5cb7b1fb5ae68d6e9eb5cd9517fce75 Change-Id: Iac74be718fd383a4dfa3cb09614684845cbdcc2b
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.