bc4d36305d
Init is no longer calling vdc with logwrapper, so it must take care of
logging to kmsg directly.
Change-Id: I529f5a95e19c08ef75e0da9a02bae1cb7187eec0
avc: denied { write } for pid=367 comm="vdc" name="kmsg" dev="tmpfs" ino=11056 scontext=u:r:vdc:s0 tcontext=u:object_r:kmsg_device:s0 tclass=chr_file permissive=0
Test: observe vdc logging in kmsg on boot and stderr on normal usage
Change-Id: Ie3678509d360f19b95cb03aeea75f29843728203
27 lines
800 B
Text
27 lines
800 B
Text
# vdc spawned from init for the following services:
|
|
# defaultcrypto
|
|
# encrypt
|
|
#
|
|
# We also transition into this domain from dumpstate, when
|
|
# collecting bug reports.
|
|
|
|
type vdc, domain;
|
|
type vdc_exec, exec_type, file_type;
|
|
|
|
unix_socket_connect(vdc, vold, vold)
|
|
|
|
# vdc sends information back to dumpstate when "adb bugreport" is used
|
|
allow vdc dumpstate:fd use;
|
|
allow vdc dumpstate:unix_stream_socket { read write getattr };
|
|
|
|
# vdc information is written to shell owned bugreport files
|
|
allow vdc shell_data_file:file { write getattr };
|
|
|
|
# Why?
|
|
allow vdc dumpstate:unix_dgram_socket { read write };
|
|
|
|
# vdc can be invoked with logwrapper, so let it write to pty
|
|
allow vdc devpts:chr_file rw_file_perms;
|
|
|
|
# vdc writes directly to kmsg during the boot process
|
|
allow vdc kmsg_device:chr_file w_file_perms;
|