binder.yaml 2.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293
  1. # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
  2. #
  3. # Copyright 2025 Google LLC
  4. #
  5. ---
  6. name: binder
  7. protocol: genetlink
  8. uapi-header: linux/android/binder_netlink.h
  9. doc: Binder interface over generic netlink
  10. attribute-sets:
  11. -
  12. name: report
  13. doc: |
  14. Attributes included within a transaction failure report. The elements
  15. correspond directly with the specific transaction that failed, along
  16. with the error returned to the sender e.g. BR_DEAD_REPLY.
  17. attributes:
  18. -
  19. name: error
  20. type: u32
  21. doc: The enum binder_driver_return_protocol returned to the sender.
  22. -
  23. name: context
  24. type: string
  25. doc: The binder context where the transaction occurred.
  26. -
  27. name: from-pid
  28. type: u32
  29. doc: The PID of the sender process.
  30. -
  31. name: from-tid
  32. type: u32
  33. doc: The TID of the sender thread.
  34. -
  35. name: to-pid
  36. type: u32
  37. doc: |
  38. The PID of the recipient process. This attribute may not be present
  39. if the target could not be determined.
  40. -
  41. name: to-tid
  42. type: u32
  43. doc: |
  44. The TID of the recipient thread. This attribute may not be present
  45. if the target could not be determined.
  46. -
  47. name: is-reply
  48. type: flag
  49. doc: When present, indicates the failed transaction is a reply.
  50. -
  51. name: flags
  52. type: u32
  53. doc: The bitmask of enum transaction_flags from the transaction.
  54. -
  55. name: code
  56. type: u32
  57. doc: The application-defined code from the transaction.
  58. -
  59. name: data-size
  60. type: u32
  61. doc: The transaction payload size in bytes.
  62. operations:
  63. list:
  64. -
  65. name: report
  66. doc: |
  67. A multicast event sent to userspace subscribers to notify them about
  68. binder transaction failures. The generated report provides the full
  69. details of the specific transaction that failed. The intention is for
  70. programs to monitor these events and react to the failures as needed.
  71. attribute-set: report
  72. mcgrp: report
  73. event:
  74. attributes:
  75. - error
  76. - context
  77. - from-pid
  78. - from-tid
  79. - to-pid
  80. - to-tid
  81. - is-reply
  82. - flags
  83. - code
  84. - data-size
  85. mcast-groups:
  86. list:
  87. -
  88. name: report