<feed xmlns='http://www.w3.org/2005/Atom'>
<title>system_core/init/stable_properties.h, branch replicant-10</title>
<subtitle>Fork of system/core
</subtitle>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/system_core/'/>
<entry>
<title>init: if vendor_init can read a property, let it be a trigger too</title>
<updated>2018-10-22T23:16:03+00:00</updated>
<author>
<name>Tom Cherry</name>
<email>tomcherry@google.com</email>
</author>
<published>2018-10-22T21:50:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/system_core/commit/?id=b35f827c97ceb24e33fb2514ff62c8636bc46f59'/>
<id>b35f827c97ceb24e33fb2514ff62c8636bc46f59</id>
<content type='text'>
There is a list of 'stable_properties' that vendor_init can use as
property triggers for Treble property compliance.  This list came about
since init parses init scripts before all partitions are mounted and
therefore before all property context files are available, such that
init cannot use the normal SELinux mechanisms for determining if a
given property is vendor_init readable.

Currently though, we require all partitions that would contain
property context files to be mounted during first stage mount, so we
can use the normal SELinux mechanisms here, so this change deprecates
the stable_properties list and moves init to use SELinux to determine
if a property can be a trigger.

Bug: 71814576
Test: vendor_init fails to use non-readable properties as a trigger
Test: vendor_init successfully uses readable properties as a trigger
Change-Id: I6a914e8c212a3418cbf4a8a07215056aad2e0162
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
There is a list of 'stable_properties' that vendor_init can use as
property triggers for Treble property compliance.  This list came about
since init parses init scripts before all partitions are mounted and
therefore before all property context files are available, such that
init cannot use the normal SELinux mechanisms for determining if a
given property is vendor_init readable.

Currently though, we require all partitions that would contain
property context files to be mounted during first stage mount, so we
can use the normal SELinux mechanisms here, so this change deprecates
the stable_properties list and moves init to use SELinux to determine
if a property can be a trigger.

Bug: 71814576
Test: vendor_init fails to use non-readable properties as a trigger
Test: vendor_init successfully uses readable properties as a trigger
Change-Id: I6a914e8c212a3418cbf4a8a07215056aad2e0162
</pre>
</div>
</content>
</entry>
<entry>
<title>export dumpstatez into stable_properties</title>
<updated>2018-10-11T09:02:58+00:00</updated>
<author>
<name>Minchan Kim</name>
<email>minchan@google.com</email>
</author>
<published>2018-10-10T10:17:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/system_core/commit/?id=b7f6c5a1cd7942ae9ff4627ee5f9ce1789fcf059'/>
<id>b7f6c5a1cd7942ae9ff4627ee5f9ce1789fcf059</id>
<content type='text'>
Vendor might want to pause/resume some operations while a bugreport is captured
so that we need to export dumpstatez into stable_properties.h for vendor to get
property event when dumpstatez launch.

Test: confirmed manually with "adb bugreport"
Bug: 117536084
Change-Id: Ib743c5e59ca20cc44470110c814d85e4cbb90c0c
Signed-off-by: Minchan Kim &lt;minchan@google.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Vendor might want to pause/resume some operations while a bugreport is captured
so that we need to export dumpstatez into stable_properties.h for vendor to get
property event when dumpstatez launch.

Test: confirmed manually with "adb bugreport"
Bug: 117536084
Change-Id: Ib743c5e59ca20cc44470110c814d85e4cbb90c0c
Signed-off-by: Minchan Kim &lt;minchan@google.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Allow vendor-init-actionable for vold-related properties</title>
<updated>2018-04-11T23:17:43+00:00</updated>
<author>
<name>Jaekyun Seok</name>
<email>jaekyun@google.com</email>
</author>
<published>2018-04-11T23:16:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/system_core/commit/?id=65ce3b2cd879e39d75012798eef348283ad8b4f3'/>
<id>65ce3b2cd879e39d75012798eef348283ad8b4f3</id>
<content type='text'>
Bug: 75987246
Bug: 73871799
Test: succeeded building and tested with taimen
Change-Id: Ifec879f07705a52501757b58b1562a97c668b8b0
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Bug: 75987246
Bug: 73871799
Test: succeeded building and tested with taimen
Change-Id: Ifec879f07705a52501757b58b1562a97c668b8b0
</pre>
</div>
</content>
</entry>
<entry>
<title>Allow vendor-init-actionable for wlan.driver.status and init.svc.surfaceflinger</title>
<updated>2018-04-05T14:08:39+00:00</updated>
<author>
<name>Jaekyun Seok</name>
<email>jaekyun@google.com</email>
</author>
<published>2018-04-05T12:20:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/system_core/commit/?id=66797804c68eac46318e19e00bf86554d30eaada'/>
<id>66797804c68eac46318e19e00bf86554d30eaada</id>
<content type='text'>
They are being used as action triggers in some devices including Pixels.
So vendor-init-actionable should be allowed for them.

Bug: 74266614
Test: building succeeded and tested on a Pixel with
PRODUCT_COMPATIBLE_PROPERTY=true

Change-Id: I713c5c1a50053f8d64e1cecd1f7ab5dc18201da1
Merged-In: I713c5c1a50053f8d64e1cecd1f7ab5dc18201da1
(cherry picked from commit 167ec7f1d255ef9754d21383a9af46b07a20bac0)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
They are being used as action triggers in some devices including Pixels.
So vendor-init-actionable should be allowed for them.

Bug: 74266614
Test: building succeeded and tested on a Pixel with
PRODUCT_COMPATIBLE_PROPERTY=true

Change-Id: I713c5c1a50053f8d64e1cecd1f7ab5dc18201da1
Merged-In: I713c5c1a50053f8d64e1cecd1f7ab5dc18201da1
(cherry picked from commit 167ec7f1d255ef9754d21383a9af46b07a20bac0)
</pre>
</div>
</content>
</entry>
<entry>
<title>Allow vendor-init-actionable for ro.board.platform and sys.boot_from_charger_mode</title>
<updated>2018-03-29T21:13:12+00:00</updated>
<author>
<name>Jaekyun Seok</name>
<email>jaekyun@google.com</email>
</author>
<published>2018-03-29T05:54:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/system_core/commit/?id=f328b0d9359a23e8ea3c1c5194ee0caa83dc5b67'/>
<id>f328b0d9359a23e8ea3c1c5194ee0caa83dc5b67</id>
<content type='text'>
ro.board.platform and sys.boot_from_charger_mode are already
public-readable, but they should be used as action triggers as well for
some products including Android Go devices.

Bug: 75987246
Test: succeeded building and tested with taimen
Change-Id: I140a8f7ef3fa9823ceced94b00a413800518c240
Merged-In: I140a8f7ef3fa9823ceced94b00a413800518c240
(cherry picked from commit 1f90ccefb6f809fd479ead55247a59378bc5908f)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
ro.board.platform and sys.boot_from_charger_mode are already
public-readable, but they should be used as action triggers as well for
some products including Android Go devices.

Bug: 75987246
Test: succeeded building and tested with taimen
Change-Id: I140a8f7ef3fa9823ceced94b00a413800518c240
Merged-In: I140a8f7ef3fa9823ceced94b00a413800518c240
(cherry picked from commit 1f90ccefb6f809fd479ead55247a59378bc5908f)
</pre>
</div>
</content>
</entry>
<entry>
<title>Allow vendor-init-actionable for ro.debuggable</title>
<updated>2018-03-28T19:21:22+00:00</updated>
<author>
<name>Jaekyun Seok</name>
<email>jaekyun@google.com</email>
</author>
<published>2018-03-28T03:21:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/system_core/commit/?id=fce960cdf491d0de6101d76292eacab2c45b29df'/>
<id>fce960cdf491d0de6101d76292eacab2c45b29df</id>
<content type='text'>
Some partners are using ro.debuggable as action trigger to config a
product differently according to its value.

Bug: 75987246
Test: succeeded building and tested taimen
Change-Id: I4cc57e7b52e17fc89e585afa0a8a10925e47fac8
Merged-In: I4cc57e7b52e17fc89e585afa0a8a10925e47fac8
(cherry picked from commit 4f214c5179b2bef7de84b8b5eb2c18fd3f7312a8)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Some partners are using ro.debuggable as action trigger to config a
product differently according to its value.

Bug: 75987246
Test: succeeded building and tested taimen
Change-Id: I4cc57e7b52e17fc89e585afa0a8a10925e47fac8
Merged-In: I4cc57e7b52e17fc89e585afa0a8a10925e47fac8
(cherry picked from commit 4f214c5179b2bef7de84b8b5eb2c18fd3f7312a8)
</pre>
</div>
</content>
</entry>
<entry>
<title>Allow vendor_init_actionable to persist.sys.usb.usbradio.config</title>
<updated>2018-03-19T22:40:16+00:00</updated>
<author>
<name>Jaekyun Seok</name>
<email>jaekyun@google.com</email>
</author>
<published>2018-03-19T00:03:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/system_core/commit/?id=56f832e561a44b5ca6f989270899dc6c6a4f65b0'/>
<id>56f832e561a44b5ca6f989270899dc6c6a4f65b0</id>
<content type='text'>
persist.sys.usb.usbradio.config can be used as an action trigger in
vendor init scripts.

Bug: 75202311
Bug: 74266614
Test: succeeded building and tested on pixels
Change-Id: I123b5ebce4bbf33f41222c2e11137d52e38ff9f8
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
persist.sys.usb.usbradio.config can be used as an action trigger in
vendor init scripts.

Bug: 75202311
Bug: 74266614
Test: succeeded building and tested on pixels
Change-Id: I123b5ebce4bbf33f41222c2e11137d52e38ff9f8
</pre>
</div>
</content>
</entry>
<entry>
<title>Export init.svc.console as an actionable property</title>
<updated>2018-03-13T21:12:43+00:00</updated>
<author>
<name>Jaekyun Seok</name>
<email>jaekyun@google.com</email>
</author>
<published>2018-03-12T01:53:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/system_core/commit/?id=3b613ccedcf191c8e89595173b46f023805c64e3'/>
<id>3b613ccedcf191c8e89595173b46f023805c64e3</id>
<content type='text'>
The state of console can be used to set up a device for debugging.

Bug: 74266614
Test: succeeded building and tested with Pixels
Change-Id: I3691fa2819594a521e05dad150550ab309a78c68
Merged-In: I3691fa2819594a521e05dad150550ab309a78c68
(cherry picked from commit cba467eeda887d2eb65edf7777c525cad23b8ebb)
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The state of console can be used to set up a device for debugging.

Bug: 74266614
Test: succeeded building and tested with Pixels
Change-Id: I3691fa2819594a521e05dad150550ab309a78c68
Merged-In: I3691fa2819594a521e05dad150550ab309a78c68
(cherry picked from commit cba467eeda887d2eb65edf7777c525cad23b8ebb)
</pre>
</div>
</content>
</entry>
<entry>
<title>Update stable_properties.h</title>
<updated>2018-01-31T12:47:09+00:00</updated>
<author>
<name>Jaekyun Seok</name>
<email>jaekyun@google.com</email>
</author>
<published>2018-01-31T09:12:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/system_core/commit/?id=cf2da29d66d641d3b2f27de886403b28804cbe7b'/>
<id>cf2da29d66d641d3b2f27de886403b28804cbe7b</id>
<content type='text'>
ro.boot.* are from kernel cmdline, and kernel is usually owned by SoC
vendor or ODM.
So those properties should be allowed as action triggers of
vendor/odm init scripts.

Additionally the state of mediadrm (/system/bin/mediadrmserver) should
be used to operate the state of drm HAL.
So init.svc.mediadrm should be whitelisted as an action trigger as well.

Bug: 36796459
Test: tested with walleye
Change-Id: Ic9f68162c577cc190f193063988ad04e42478e6e
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
ro.boot.* are from kernel cmdline, and kernel is usually owned by SoC
vendor or ODM.
So those properties should be allowed as action triggers of
vendor/odm init scripts.

Additionally the state of mediadrm (/system/bin/mediadrmserver) should
be used to operate the state of drm HAL.
So init.svc.mediadrm should be whitelisted as an action trigger as well.

Bug: 36796459
Test: tested with walleye
Change-Id: Ic9f68162c577cc190f193063988ad04e42478e6e
</pre>
</div>
</content>
</entry>
<entry>
<title>Apply the whitelist of actionable system properties</title>
<updated>2018-01-17T19:38:01+00:00</updated>
<author>
<name>Jaekyun Seok</name>
<email>jaekyun@google.com</email>
</author>
<published>2018-01-16T03:51:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.replicant.us/replicant-next/system_core/commit/?id=eeb21885545f25606498feee0ad3f1f9b29e44e8'/>
<id>eeb21885545f25606498feee0ad3f1f9b29e44e8</id>
<content type='text'>
This whitelist will be applied only when
ro.actionable_compatible_property.enabled is true.

Bug: 38146102
Test: tested on walleye with ro.actionable_compatible_property.enabled=true
Change-Id: Ifd7211396b53e50a06d79e7c67224e2b38ef7c9d
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This whitelist will be applied only when
ro.actionable_compatible_property.enabled is true.

Bug: 38146102
Test: tested on walleye with ro.actionable_compatible_property.enabled=true
Change-Id: Ifd7211396b53e50a06d79e7c67224e2b38ef7c9d
</pre>
</div>
</content>
</entry>
</feed>
