[PATCH v2 0/3] rust_binder: error line numbers and failed_transaction_log

[Alice Ryhl <aliceryhl@google.com>]

When diagnosing Binder issues, it's useful to know what the most recent
failed transactions are, so include a transaction log with this content
matching the C Binder transaction log.

While we're at it, improve the line number information emitted by Rust
Binder using #[track_caller].

Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
Changes in v2:
- Retry on 0 in next_debug_id() so 0 is never returned on wrap-around.
- Handle debug_id wrap-around in TransactionLog::add using wrapping_sub.
- Link to v1: https://lore.kernel.org/r/20260930-binder-transaction-log-v1-0-3d832fb30388@google.com

---
Alice Ryhl (3):
      rust_binder: never return 0 from next_debug_id
      rust_binder: track caller location in BinderError
      rust_binder: add transaction_log and failed_transaction_log

 drivers/android/binder/context.rs             |   8 +-
 drivers/android/binder/error.rs               |  39 +++++
 drivers/android/binder/process.rs             |   5 +-
 drivers/android/binder/rust_binder_internal.h |   1 +
 drivers/android/binder/rust_binder_main.rs    |  31 +++-
 drivers/android/binder/rust_binderfs.c        |  19 +++
 drivers/android/binder/thread.rs              |  12 +-
 drivers/android/binder/transaction.rs         | 197 +++++++++++++++++++++++++-
 8 files changed, 302 insertions(+), 10 deletions(-)
---
base-commit: 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e
change-id: 20260930-binder-transaction-log-94989f47b142

Best regards,
-- 
Alice Ryhl <aliceryhl@google.com>