[roll] Roll fuchsia [kernel][scheduler] Use a CLT in Dump to defer DLog::Write Signal

Create an active chain lock transaction in Scheduler::Dump and
Scheduler::DumpActiveThread before calling fprintf to work around a
re-entrancy issue involving DLog::Write and Event::Signal.  See
b/331847876 for details.

Original-Bug: 331847876
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1048030
Original-Revision: a98fae330e3b878e7c4a3738e99d113caedf31b2
GitOrigin-RevId: 30fb065b347aa923b8a07dad22d1a9a592aeaf89
Change-Id: Ia4372a8cdfe7a98b4c0b289af087800e783906aa
1 file changed
tree: 80dc7d4de448d7a8dde1aaad78d42e5ff6485af8
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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.