libbinder_ndk: clarify local AIBinder_linkToDeath
When a binder is local, process death means that the client calling
linkToDeath will also die. In this case, there is no need to use a
death recipient, so an error is returned.
Bug: 112664205
Test: atest android.binder.cts
Change-Id: I675637e937c1ac7a584a2d97bb1238e5b9f3e030
diff --git a/libs/binder/ndk/include_ndk/android/binder_ibinder.h b/libs/binder/ndk/include_ndk/android/binder_ibinder.h
index f237e69..c222c16 100644
--- a/libs/binder/ndk/include_ndk/android/binder_ibinder.h
+++ b/libs/binder/ndk/include_ndk/android/binder_ibinder.h
@@ -207,6 +207,8 @@
* null. The exact cookie must also be used to unlink this transaction (see AIBinder_linkToDeath).
* This function may return a binder transaction failure. The cookie can be used both for
* identification and holding user data.
+ *
+ * If binder is local, this will return STATUS_INVALID_OPERATION.
*/
binder_status_t AIBinder_linkToDeath(AIBinder* binder, AIBinder_DeathRecipient* recipient,
void* cookie) __INTRODUCED_IN(29);