On 10/28/2014 10:27 AM, [email protected] wrote: > Hi Stephen, > We found one clue need your help to comment. If base ROM default is > Permissive mode then OTA to target ROM become Enforcing mode. > Whether SELinux default mode change will cause this unlabel symptom? Due to > we already check you mentioned related commit and all commits include our L > codebase. > > M8 Base ROM > Full ROM flash with test-keys: Permissive mode > OTA test-keys: Enforcing > > M8 Target ROM > Full ROM flash with test-keys: Enforcing
No, that shouldn't matter with respect to the existence of unlabeled files. The first time you upgrade from pre-L to L, it should perform a relabel of /data/data, and then on any subsequent upgrade it will perform a relabel if /seapp_contexts has changed since the last upgrade. It determines whether /seapp_contexts has changed by saving a hash of the file to /data/system/seapp_hash and comparing that to the hash of the current /seapp_contexts file. PackageManagerService calls SELinuxMMAC.shouldRestorecon() to check whether the relabel is required; if so, it calls mInstaller.restoreconData for each apps as it is loaded, and then once it is done loading all apps, it calls SELinuxMMAC.setRestoreconDone() to write out the new /data/system/seapp_hash file. It is possible that something went wrong with the restorecon and thus it never correctly completed during the upgrade. Can't really tell that without seeing the logcat output for all of the upgrades done on the device starting from the one that preceded any L snapshot. You didn't send me the dmesg or logcat output with the avc: denied messages from your ls -ZR command. I assume you have a way to get real root on the device, not just root in the shell domain? Otherwise you can't really get access to all of the information. _______________________________________________ Seandroid-list mailing list [email protected] To unsubscribe, send email to [email protected]. To get help, send an email containing "help" to [email protected].
