junyulai 646ee4621c Ignore the asynchronous result while stopping keepalive ...

Currently, onStopped callback are synchronizely triggered when
stop() was called, since the framework don't really care
about the result of stopping keepalive.

However, if keepalive failed to stop for some reason, the
handleStopKeepalive was called mistakenly and trigger additional
callback that fail the test case.

This commit is the behavior change prior to state machine
refactoring, and introduce a stopping state for ignoring the
result in the stopping state.

Bug: 129512753
Bug: 123988249
Test: 1. atest com.android.server.ConnectivityServiceTest \
         #testNattSocketKeepalives --generate-new-metrics 100
      2. atest FrameworksNetTests

Change-Id: I4fa94e0740ba488fb5fe7ac7c3812c195dd0ec4c

2019-04-01 16:22:02 +08:00

core

Block unpriviledged apps which create keepalives with null fd

2019-03-27 19:51:08 +08:00

services/core

Ignore the asynchronous result while stopping keepalive

2019-04-01 16:22:02 +08:00

tests/net

Merge changes I0baf582f,I4bba01ba

2019-03-28 00:53:20 +00:00

Description

android_packages_modules_Connectivity

189 MiB

Languages

Java 81.4%

Kotlin 7.7%

AIDL 4.5%

C++ 4.5%

C 1.7%

Other 0.1%