[roll] Roll fuchsia [kernel][mutex] Don't concurrently access should_clear_

Don't access CriticalMutex::should_clear after calling Mutex::Release.

This change fixes a data race bug in CriticalMutex.

Original-Bug: 104468
Original-Fixed: 105424
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/705308
Original-Revision: 90786725d8eeb8d01e86d42cf73fc4fff3afc300
GitOrigin-RevId: abc2332ae66e45e1fb8dd226104e21978ec03f70
Change-Id: I3259f718ed23d74c3d70a949d74d3a587f977528
1 file changed
tree: 307326a061c180b161bf4dd89e17cb20666bbf60
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.