[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20260123175702.2154348-1-cmllamas@google.com>
Date: Fri, 23 Jan 2026 17:57:02 +0000
From: Carlos Llamas <cmllamas@...gle.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Arve Hjønnevåg" <arve@...roid.com>, Todd Kjos <tkjos@...roid.com>,
Christian Brauner <brauner@...nel.org>, Carlos Llamas <cmllamas@...gle.com>,
Alice Ryhl <aliceryhl@...gle.com>
Cc: kernel-team@...roid.com, linux-kernel@...r.kernel.org, stable@...nel.org,
Steven Moreland <smoreland@...gle.com>, Todd Kjos <tkjos@...gle.com>
Subject: [PATCH] binder: fix BR_FROZEN_REPLY error log
The error logging for failed transactions is misleading as it always
reports "dead process or thread" even when the target is actually
frozen. Additionally, the pid and tid are reversed which can further
confuse debugging efforts. Fix both issues.
Cc: stable@...nel.org
Cc: Steven Moreland <smoreland@...gle.com>
Fixes: a15dac8b2286 ("binder: additional transaction error logs")
Signed-off-by: Carlos Llamas <cmllamas@...gle.com>
---
drivers/android/binder.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/android/binder.c b/drivers/android/binder.c
index 535fc881c8da..2837162e73e8 100644
--- a/drivers/android/binder.c
+++ b/drivers/android/binder.c
@@ -3812,8 +3812,9 @@ static void binder_transaction(struct binder_proc *proc,
return;
err_dead_proc_or_thread:
- binder_txn_error("%d:%d dead process or thread\n",
- thread->pid, proc->pid);
+ binder_txn_error("%d:%d %s process or thread\n",
+ proc->pid, thread->pid,
+ return_error == BR_FROZEN_REPLY ? "frozen" : "dead");
return_error_line = __LINE__;
binder_dequeue_work(proc, tcomplete);
err_translate_failed:
--
2.52.0.457.g6b5491de43-goog
Powered by blists - more mailing lists