commit | a3d6dae8b58585d02aa6d66f7f607e05d0fa86a4 | [log] [tgz] |
---|---|---|
author | Stephen Demos <sdemos@fuchsia.infra.roller.google.com> | Wed Apr 09 10:32:26 2025 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 09 10:34:15 2025 -0700 |
tree | ee98c92497bb396765e57514f20766e66cb4b05c | |
parent | bb6514849aa684104b01d47e51edba34462e15ee [diff] |
[roll] Roll fuchsia [sherlock] remove gpt type guid remapping This metadata block would tell the gpt driver to remap partitions with certain labels to have specified type guids. The two consumers of partition metadata are fshost and the paver. Fshost doesn't use type guids for identifying partitions. The paver does, mostly via FindPartition, but there is an issue with the implementation - FindPartition reads the gpt metadata off the disk so it ignores the remapping (which is at the driver level), but then it passes the non-remapped type guid into OpenBlockPartition, which _does_ use the remapped type guid to find the partition and open a connection. Therefore, if the remapping applied to any partitions in use, OTAs would already be broken for sherlock. Since they aren't, we can assume the remapping is a no-op. See the bug for a slightly more detailed discussion. Original-Bug: 393194863 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1238668 Original-Revision: 500a41a1e4aed48d1035d6f73a2612dd959043f4 GitOrigin-RevId: 3533cacafb7c8a828374030304632d9d5add444b Change-Id: I05104bc49115b64793c754361c8b7cea221059f8
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
.