[roll] Roll fuchsia [kernel][tracing] Fix duplicate flow IDs in futex, pager, and IPC

Resolve flow_duplicate_id errors in Perfetto trace processing by
ensuring all kernel-emitted flow begin events are properly balanced or
uniquely correlated:

1. Futex Contention (futex_context.cc):
   Emit LOCK_TRACE_FLOW_END in FutexWait's non-OK cleanup path (e.g.
   timeout, suspension, or interruption) so contention flows do not
   remain perpetually active in the trace processor.
2. Pager Requests (pager_proxy.cc, pager_proxy.h):
   Use flow_id_generate() instead of casting &packet_ to uintptr_t.
   Because packet_ is a member variable reused across consecutive
   requests, pointer recycling caused duplicate flow begin collisions
   if a previous flow was cancelled or lost.
3. Channel IPC (channel_dispatcher.cc):
   Use the message packet pointer address for ChannelMessageFlowId
   when txid is not kernel-generated (!IsKernelGeneratedTxid), rather
   than only when txid == 0. This prevents backlog collisions when
   userspace clients queue multiple requests with non-zero txids.

Original-Original-Fixed: 545311368
Test: fx test futex-ownership-test
Test: Captured trace and verified 0 kernel flow_duplicate_id errors
Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1769097
Original-Original-Revision: 858b7a62af107a3e41bcce3c1b3ab783b9fe7a88
GitOrigin-RevId: 728f37d1eefc40e22210cdd7cb414e6bdad278c6
Change-Id: I4c434a9b4b028e873180d5c451c936b448dfa12f
1 file changed
tree: 10ae8e73ed7a4d90b7f9c4b7187aa430a45738c5
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. 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 in one of the communication channels documented at get involved.

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.