linux-kernel - [PATCH v3 0/1] binder: return pending info for frozen async txns

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20221123201654.589322-1-dualli@chromium.org>
Date:   Wed, 23 Nov 2022 12:16:53 -0800
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 v3 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 adds a new return value, BR_TRANSACTION_PENDING_FROZEN, 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
v2: protect proc->is_frozen with lock, fix typo in comments
v3: rename BR_TRANSACTION_PENDING to BR_TRANSACTION_PENDING_FROZEN to
    signify the frozen scenario and avoid potential confusion

Li Li (1):
  binder: return pending info for frozen async txns

 drivers/android/binder.c            | 32 +++++++++++++++++++++++------
 drivers/android/binder_internal.h   |  3 ++-
 include/uapi/linux/android/binder.h |  7 ++++++-
 3 files changed, 34 insertions(+), 8 deletions(-)

-- 
2.38.1.584.g0f3c55d4c2-goog