diff options
| author | 2021-09-22 15:00:56 -0700 | |
|---|---|---|
| committer | 2021-09-22 15:00:56 -0700 | |
| commit | 052a957a90c4a3ea804f4e7239d7054011a0b1b5 (patch) | |
| tree | 6d582755807d21fdc9747efb2a9b514c9e4312d2 /libs/binder/RpcState.cpp | |
| parent | abecf2e90ab29259a69bc472b6015485f9e1bc2b (diff) | |
libbinder: don't ignore sendDecStrong error
I am not sure why this was ignored before, but I can't think of any
reason why it should be. Fail hard fail fast.
Note: this is being submitted independently in preparation for a series
of refcount changes related to performance.
Bug: 182940634
Test: binderRpcTest
Change-Id: Ifcc0bf96952a368c4ad5620b3f1d2d17feac40c5
Diffstat (limited to 'libs/binder/RpcState.cpp')
| -rw-r--r-- | libs/binder/RpcState.cpp | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/libs/binder/RpcState.cpp b/libs/binder/RpcState.cpp index dcba837a85..df935fe9e3 100644 --- a/libs/binder/RpcState.cpp +++ b/libs/binder/RpcState.cpp @@ -166,9 +166,7 @@ status_t RpcState::onBinderEntering(const sp<RpcSession>& session, uint64_t addr // We have timesRecd RPC refcounts, but we only need to hold on to one // when we keep the object. All additional dec strongs are sent // immediately, we wait to send the last one in BpBinder::onLastDecStrong. - (void)session->sendDecStrong(address); - - return OK; + return session->sendDecStrong(address); } // we don't know about this binder, so the other side of the connection |