diff options
| author | junyulai <junyulai@google.com> | 2019-09-03 18:51:04 +0800 |
|---|---|---|
| committer | junyulai <junyulai@google.com> | 2020-08-20 11:00:08 +0800 |
| commit | eed8c6bb26bcb2ae4a013f4148dad4c4d6069287 (patch) | |
| tree | 7977bcaa5779d42bcbf147657ac618170cb08771 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 5063505fab8d1eb986cf59851289a387114e49cc (diff) | |
Notify the keepalive is stopped after the slot has been released
Currently, the callbacks of stopping were fired when stop procedure
is started, because the upper layer apps only care about the reason
of stopping instead of stopping result. Thus, there is no need to
wait for the result comes back. However, this behavior generates
races if apps want to re-start keepalive immediately since the
resources are not released yet.
Fix: 134891441
Fix: 140305589
Test: atest com.android.server.ConnectivityServiceTest#testPacketKeepalives \
--rerun-until-failure 1000
Change-Id: I987776a9211a50e964c4675b747bc10e203750f1
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions