diff options
author | Christopher Tate <ctate@google.com> | 2012-09-13 16:19:44 -0700 |
---|---|---|
committer | Christopher Tate <ctate@google.com> | 2012-09-13 19:15:54 -0700 |
commit | 78d2a66ac12e4c8f1303225514f573fb53af1dd9 (patch) | |
tree | 34125548e558c48d3677d43c5f9b4e7cde4d5f48 /core/tests/coretests/AndroidManifest.xml | |
parent | 79d45660f2a83a7a771acf82c0bd0efed806abfa (diff) | |
download | frameworks_base-78d2a66ac12e4c8f1303225514f573fb53af1dd9.zip frameworks_base-78d2a66ac12e4c8f1303225514f573fb53af1dd9.tar.gz frameworks_base-78d2a66ac12e4c8f1303225514f573fb53af1dd9.tar.bz2 |
Fix Settings writes to a different user
Oops. Stacked bugs: first, the desired user handle was not properly
being passed from the call() entry point to the database operations;
then on top of that, the client-side cache management was still
looking in the local user's cache for the data, so a request to read
a different user's settings would return the local user's instead if
that key was already known to the local user's cache.
Reads and writes of a different user's settings are now uncached,
so they're relatively much slower. They're rare, however, so this
is not something to worry about unless we encounter a real world
case where it's a significant factor.
This CL also adds a bit of cross-user settings read/write testing
to the existing provider suite. These new tests caught both the
known wrong-user-write bug and discovered the client-side cache
bug, so yay.
Finally, the existing wholesale mutual-exclusion approach would
deadlock in certain circumstances due to the fact that the
settings database creation code might have to call out to the
Package Manager while populating the bookmark/shortcut table,
and the Package Manager would then call back into the settings
provider in the course of handling that request. The synchronization
regime has been significantly tightened up now: now the database
code [which is known to deal with concurrency itself] is allowed
to cope with multiple parallel openers of the same db; this
allows the settings provider to avoid calling out to other parts
of the system even implicitly while its internal lock is held.
Change-Id: Ib77d445b4a2ec658cc5c210830f6977c981f87ed
Diffstat (limited to 'core/tests/coretests/AndroidManifest.xml')
-rw-r--r-- | core/tests/coretests/AndroidManifest.xml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/core/tests/coretests/AndroidManifest.xml b/core/tests/coretests/AndroidManifest.xml index dcd1bab..41f8536 100644 --- a/core/tests/coretests/AndroidManifest.xml +++ b/core/tests/coretests/AndroidManifest.xml @@ -69,6 +69,10 @@ <uses-permission android:name="com.google.android.googleapps.permission.GOOGLE_AUTH" /> <uses-permission android:name="com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES" /> + <uses-permission android:name="android.permission.MANAGE_USERS" /> + <uses-permission android:name="android.permission.INTERACT_ACROSS_USERS" /> + <uses-permission android:name="android.permission.INTERACT_ACROSS_USERS_FULL" /> + <uses-permission android:name="android.permission.RECEIVE_SMS"/> <uses-permission android:name="android.permission.INTERNET" /> <uses-permission android:name="android.permission.READ_CONTACTS" /> |