[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221103190549.3446167-1-dualli@chromium.org>
Date: Thu, 3 Nov 2022 12:05:48 -0700
From: Li Li <dualli@...omium.org>
To: dualli@...gle.com, gregkh@...uxfoundation.org, arve@...roid.com,
tkjos@...roid.com, maco@...roid.com, joel@...lfernandes.org,
brauner@...nel.org, cmllamas@...gle.com, surenb@...gle.com,
arnd@...db.de, masahiroy@...nel.org, devel@...verdev.osuosl.org,
linux-kernel@...r.kernel.org, hridya@...gle.com,
smoreland@...gle.com
Cc: kernel-team@...roid.com
Subject: [PATCH v1 0/1] binder: return pending info for frozen async txns
From: Li Li <dualli@...gle.com>
User applications need to know if their binder transactions reach a
frozen process or not. For sync binder calls, Linux kernel already
has a dedicated return value BR_FROZEN_REPLY, indicating this sync
binder transaction will be rejected (similar to BR_DEAD_REPLY) as the
target process is frozen. But for async binder calls, the user space
application doesn't have a way to know if the target process is frozen.
This patch add a new return value, BR_TRANSACTION_PENDING, to fix this
issue. Similar to BR_TRANSACTION_COMPLETE, it means the async binder
transaction has been put in the queue of the target process, but it's
waiting for the target process to be unfrozen.
v1: checkpatch.pl --strict passed
Li Li (1):
binder: return pending info for frozen async txns
drivers/android/binder.c | 23 ++++++++++++++++++++---
drivers/android/binder_internal.h | 3 ++-
include/uapi/linux/android/binder.h | 7 ++++++-
3 files changed, 28 insertions(+), 5 deletions(-)
--
2.38.1.431.g37b22c650d-goog
Powered by blists - more mailing lists