[roll] Roll fuchsia [fxfs] Add lock checks for Keys mutations

This revealed a bug in the tracking of new objects in a transaction; we
were removing the object from the list of new objects whenever *any*
mutation relevant to that object was removed, when we should only do so
for an ObjectKeyData::Object mutation being removed (symmetric with how
objects get added into the new_objects tracking in the first place).

Original-Fixed: 122975
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/862230
Original-Revision: 0c14e890754f6582a0b9773a9fc0ee4d2c976896
GitOrigin-RevId: 2c8d6037018cfe194b980be6e4ab20bc8bf1fd2e
Change-Id: If421cbc1172aa606b2562bf8d46d708bd7400cfa
1 file changed
tree: 2e7e3fdecd4f585bfa28f29ba10b9eb684056d5d
  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.