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@kernel.org
Cc: Steven Moreland <smoreland@google.com>
Fixes: a15dac8b2286 ("binder: additional transaction error logs")
Signed-off-by: Carlos Llamas <cmllamas@google.com>
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
Link: https://patch.msgid.link/20260123175702.2154348-1-cmllamas@google.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

authored by Carlos Llamas and committed by Greg Kroah-Hartman 1769f90e d0472481

+3 -2
+3 -2
drivers/android/binder.c
··· 3824 3824 return; 3825 3825 3826 3826 err_dead_proc_or_thread: 3827 - binder_txn_error("%d:%d dead process or thread\n", 3828 - thread->pid, proc->pid); 3827 + binder_txn_error("%d:%d %s process or thread\n", 3828 + proc->pid, thread->pid, 3829 + return_error == BR_FROZEN_REPLY ? "frozen" : "dead"); 3829 3830 return_error_line = __LINE__; 3830 3831 binder_dequeue_work(proc, tcomplete); 3831 3832 err_translate_failed: