Fix fsck-related denials with encrypted userdata.
Allow error reporting via the pty supplied by init. Allow vold to invoke fsck for checking volumes. Addresses denials such as: avc: denied { ioctl } for pid=133 comm="e2fsck" path="/dev/pts/0" dev="devpts" ino=3 scontext=u:r:fsck:s0 tcontext=u:object_r:devpts:s0 tclass=chr_file avc: denied { execute } for pid=201 comm="vold" name="e2fsck" dev="mmcblk0p25" ino=98 scontext=u:r:vold:s0 tcontext=u:object_r:fsck_exec:s0 tclass=file These denials show up if you have encrypted userdata. Change-Id: Idc8e6f83a0751f17cde0ee5e4b1fbd6efe164e4c Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
This commit is contained in:
parent
92dfa31f78
commit
cedee697c3
2 changed files with 4 additions and 1 deletions
2
fsck.te
2
fsck.te
|
@ -10,7 +10,7 @@ init_daemon_domain(fsck)
|
|||
allow fsck tmpfs:chr_file { read write ioctl };
|
||||
|
||||
# Inherit and use pty created by android_fork_execvp_ext().
|
||||
allow fsck devpts:chr_file { read write };
|
||||
allow fsck devpts:chr_file { read write ioctl };
|
||||
|
||||
# Run e2fsck on block devices.
|
||||
# TODO: Assign userdata and cache block device types to the corresponding
|
||||
|
|
3
vold.te
3
vold.te
|
@ -38,6 +38,9 @@ allow vold sysfs:file rw_file_perms;
|
|||
|
||||
write_klog(vold)
|
||||
|
||||
# Run fsck.
|
||||
allow vold fsck_exec:file rx_file_perms;
|
||||
|
||||
# Log fsck results
|
||||
allow vold fscklogs:dir rw_dir_perms;
|
||||
allow vold fscklogs:file create_file_perms;
|
||||
|
|
Loading…
Reference in a new issue