No description
5a8a2d2b13
We stop supplicant by sending a "terminate" control command. init then updates the system property init.svc.wpa_supplicant when the supplicant has stopped. The framework gets notified of a successful supplicant stop through a supplicant event. It can happen that the framework has been notified of a supplicant stop, but the init process has not set the system property and thus when the framework tries to connect to the supplicant again, it can immediately return saying the supplicant is already running. Avoid this race, by ensuring the call from framework to close supplicant connection polls for the update by init process that the system property indicates supplicant has stopped. Bug: 5166494 Change-Id: Ie74a8cf39fa56ae557ea6bbbcba7865301620c42 |
||
|---|---|---|
| audio | ||
| include/hardware_legacy | ||
| power | ||
| qemu | ||
| qemu_tracing | ||
| uevent | ||
| vibrator | ||
| wifi | ||
| Android.mk | ||
| CleanSpec.mk | ||
| MODULE_LICENSE_APACHE2 | ||
| NOTICE | ||
| qemu.h | ||