[roll] Roll fuchsia [kernel][lockdep] Don't "clear" last_reported_ on reentrant Acquires

When lockdep reports an error, it may end up perfoming Acquires on
locks that are part of the error report code path (think printf and
debuglog). There is already a mechanism for detecting and handling
reentrancy, reporting_disabled().  Check whether reporting is disabled
before setting last_reported_ to success.

Original-Bug: 72537
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/504546
Original-Revision: 43a45307a5dad52b09a3d7e5509485591e21e506
GitOrigin-RevId: 7200a21f446cbe4aa53562c5cc123eae1acd2888
Change-Id: Ib6ed32979d568cf3fb2ca06ff05897754b58bb62
1 file changed
tree: 0dfccb9c37ddd274571056e63dcb6921ff73fbd7
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. firmware
  8. flower
  9. jiri.lock
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
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.