As show in screenshot:
before error log
Access denied finding property "persist.vendor.log.tel_dbg"
there is another warning:
type=1400 audit(xxx): avc: denied { read } for xxx
which is the reason for above error Access denied finding property
Example to show the root cause of Access denied finding property
I encount similar error:
com.gsma.rcs W/com.gsma.rcs: type=1400 audit(0.0:526384): avc: denied { read } for name="u:object_r:vendor_displayfeature_prop:s0" dev="tmpfs" ino=16384 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:vendor_displayfeature_prop:s0 tclass=file permissive=0
Exapnation:
Action
:read
Actor
=scontext
=source context
:untrusted_app_25
Object
=tcontext
=target context
:vendor_displayfeature_prop
- Note:
- corresponding later:
ro.vendor.df.effect.conflict
object_r
=object read
?
Result
=tclass
=target class
:file
permissive
=permissive mode
:0
- 0 permissive:not allow = denied
- background:
- selinux has two mode:
- permissive mode
- enforcing mode
- during Android device booting, you can use kernel parameter to config mode:
androidboot.selinux=permissive
- or
androidboot.selinux=enforcing
Translate to human readable words:
the untrusted_app_25 want to read the vendor_displayfeature_prop, which type is file
but due to NOT permissive mode, Android SELinux denied (according to OEM built-in configuration of SELinux)
which cause the following output error log:
com.gsma.rcs E/libc: Access denied finding property "ro.vendor.df.effect.conflict"
How to fix avc: denied
error ?
refer official doc:
Validating SELinux | Android Open Source Project
use audit2allow
maybe can fix it.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…