| commit | 7bf3b51e182cffdd0581f2f84e018bf643d0e0aa | [log] [tgz] |
|---|---|---|
| author | John Grossman <johngro@fuchsia.infra.roller.google.com> | Wed May 22 21:14:46 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 22 14:17:35 2024 -0700 |
| tree | 893eb83bbd51e5b77a0258ad7980f890f98873e5 | |
| parent | b695fd3b8f7c33339bc97559171fae83dce36e6c [diff] |
[roll] Roll fuchsia [kernel][chainlock] Be sure to watch the proper CPU when backing off. When encountering a ChainLock conflict and backing off, remember which CPU we had the conflict on before unregistering our active CLT and waiting for the lock we wanted to be released. Failure to do this can lead to a situation where we migrate to a different CPU which _just happens_ to have the same conflict ID as the CPU we just came from. If we stay on this CPU forever, and nothing ever generates a new conflict on our new CPU, we will just stay stuck forever. See the detailed write-up in b/341370301 if you are interested in the precise sequence. Original-Fixed: 341370301 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1052096 Original-Revision: 48ba01297af58e2e4f08712dc757c9ac9c9637ad GitOrigin-RevId: 385b6f9acddbfa7edc30de881bc30828843440e1 Change-Id: Ib2d53c4823ffabd834caef33be01b3d50b024f14
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 via the IRC channel #fuchsia on Freenode.
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.