[roll] Roll fuchsia [starnix] Use interruptible locks for append

Before this CL, a write would take a RwLock to ensure that O_APPEND
write were atomics. It means that if a append write was blocked, and a second
write was started, it could not be interrupted before the first one
has finish, even if it should have been interrupte because of signals.

This CL introduce locks that can be interrupted, and uses it for the
append lock.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/855296
Original-Revision: 81c553e7898fe9f476df7b7e9ac4efc4901f1537
GitOrigin-RevId: 826893ef261ca68d5a76dda95e93ac77be22fd38
Change-Id: I15f8fc507bdac9d1190c02d53f00010d7065d176
1 file changed
tree: 515c44d7c46f25215be9a32fa42065e8d2809e60
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. 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.