replicant/core/logd/README.property, branch master Patches not merged yet, used for building and testing them Use ro.logd.kernel for kernel logcat 2018-01-02T18:47:50+00:00 Siarhei Vishniakou svv@google.com 2017-12-28T22:13:22+00:00 e8ed36b6b3b685a73361a1005f94d5ba0f1fb121 Prevent a possible DOS of the kernel logs because the runtime result could differ from the boottime result. Test: adb bugreport, then examine kernel log Change-Id: I140fd465f2e691c751d92af50dbdf95e23c121d8 
Prevent a possible DOS of the kernel logs because the runtime result
could differ from the boottime result.

Test: adb bugreport, then examine kernel log
Change-Id: I140fd465f2e691c751d92af50dbdf95e23c121d8
logd: Add support for ro.logd.auditd.[main|events] 2017-01-03T17:44:42+00:00 Mark Salyzyn salyzyn@google.com 2016-12-29T23:16:06+00:00 ce80da301836cfa40c7a6424034f0743bbca9add log selinux audit messages boolean (true or false, default true) selection for logging destinations: ro.logd.auditd - turn on logd.auditd to pick up violations. ro.logd.auditd.dmesg - to the kernel log. ro.logd.auditd.main - to the "main" log buffer. ro.logd.auditd.events - to the "events" log buffer. We used to also read logd.auditd.dmesg and persist.logd.auditd.dmesg which do not get refreshed when /data mounts internally. This is a confusing state as these properties will be read after a logd crash and restart, adjusting the behavior of the logger. Same can be said for logd.auditd as well. Drop reading these other parameters. Test: manual set r/o parameters, stop/start logd to confirm behavior Bug: 33969000 Bug: 27878170 Change-Id: I1a6bb4a903074c9aa7b227cf583a0094d49cbefd 
log selinux audit messages boolean (true or false, default true)
selection for logging destinations:

ro.logd.auditd - turn on logd.auditd to pick up violations.
ro.logd.auditd.dmesg - to the kernel log.
ro.logd.auditd.main - to the "main" log buffer.
ro.logd.auditd.events - to the "events" log buffer.

We used to also read logd.auditd.dmesg and persist.logd.auditd.dmesg
which do not get refreshed when /data mounts internally.  This is a
confusing state as these properties will be read after a logd crash
and restart, adjusting the behavior of the logger.  Same can be said
for logd.auditd as well.  Drop reading these other parameters.

Test: manual set r/o parameters, stop/start logd to confirm behavior
Bug: 33969000
Bug: 27878170
Change-Id: I1a6bb4a903074c9aa7b227cf583a0094d49cbefd
Merge \"logcatd: trampoline persist.logd.logpersistd to logd.logpersistd\" 2016-07-13T18:02:23+00:00 Mark Salyzyn salyzyn@google.com 2016-07-13T18:02:23+00:00 6fb57f996a0ee4708b7acfb5979ea8ee863cbee0 am: 3ba829c75c Change-Id: Iec3c591d5121be9451597e90b9a6467d7c9a6986 
am: 3ba829c75c

Change-Id: Iec3c591d5121be9451597e90b9a6467d7c9a6986
logcatd: trampoline persist.logd.logpersistd to logd.logpersistd 2016-07-08T18:06:06+00:00 Mark Salyzyn salyzyn@google.com 2016-07-07T16:24:51+00:00 2591d483c83a09eb8689e6e7869b4ac0bfe418db Best practices so that device can set logd.logpersistd properties. Values can be overriden with trampolines for persist.logd.logpersistd values except as designed for empty content to keep out of the way. This allows us to set logd.logpersistd* for a non-persistent collection that does not survive a reboot, and to use persist.logd.logpersistd* for persistent collection that does survive a reboot. Added logd.logpersistd.enable to gate when logpersist service can be run allowing the properties to be adjusted safely prior to this state as is the case for device property. NB: /init will complain when trying to trampoline an empty property, this is acceptable for functionality, but may be considered annoying from the logging perspective. Bug: 28936216 Bug: 29831823 Change-Id: I97317e8eedfae4daa8e3ef39e64e7c5c23d8b573 
Best practices so that device can set logd.logpersistd properties.
Values can be overriden with trampolines for persist.logd.logpersistd
values except as designed for empty content to keep out of the way.

This allows us to set logd.logpersistd* for a non-persistent collection
that does not survive a reboot, and to use persist.logd.logpersistd*
for persistent collection that does survive a reboot.

Added logd.logpersistd.enable to gate when logpersist service can be
run allowing the properties to be adjusted safely prior to this state
as is the case for device property.

NB: /init will complain when trying to trampoline an empty property,
    this is acceptable for functionality, but may be considered
    annoying from the logging perspective.

Bug: 28936216
Bug: 29831823
Change-Id: I97317e8eedfae4daa8e3ef39e64e7c5c23d8b573
resolve merge conflicts of a742d10 to nyc-dev-plus-aosp 2016-06-14T22:55:40+00:00 Sami Tolvanen samitolvanen@google.com 2016-06-14T22:55:40+00:00 589994504a4ffe427a02f01c7c151bad9405d2bf Change-Id: Icf3257ee8a47f31ba812a5f47899b8022f4eedb7 
Change-Id: Icf3257ee8a47f31ba812a5f47899b8022f4eedb7
Revert "logd: enforce policy integrity" 2016-06-14T18:14:51+00:00 Sami Tolvanen samitolvanen@google.com 2016-06-14T18:04:43+00:00 a742d1027784a54c535cff69b375a9f560893155 This reverts commit 0bdad0f231103db89f2c0931616dd78309258d3b. Bug: 26902605 Change-Id: I6ce8fa7bef63c45821628265c379970eb64963a2 
This reverts commit 0bdad0f231103db89f2c0931616dd78309258d3b.

Bug: 26902605
Change-Id: I6ce8fa7bef63c45821628265c379970eb64963a2
logd: enforce policy integrity 2016-02-22T22:00:43+00:00 Sami Tolvanen samitolvanen@google.com 2016-02-05T22:27:52+00:00 0bdad0f231103db89f2c0931616dd78309258d3b If a SELinux policy change or a switch to permissive mode is detected on a user build, restart the device into safe mode, and keep it there until an OTA is applied or user data is wiped. This change deprecates the ro.logd.auditd property. Needs matching changes from I781c3059ea8d4fb2f0c923e4488b1932d69678d3 Ica825cf2af74f5624cf4091544bd24bb5482dbe7 Id3ca7889ede30b54b7af73dd50653ca1a20d59aa Bug: 26902605 Change-Id: Idcdc5bff133f13c1267f0ec0a75cc8cf1ddbda0d (cherry picked from commit d122ee65b66b5b33d51302dabbaa0d6c84597549) 
If a SELinux policy change or a switch to permissive mode is detected
on a user build, restart the device into safe mode, and keep it there
until an OTA is applied or user data is wiped.

This change deprecates the ro.logd.auditd property.

Needs matching changes from
  I781c3059ea8d4fb2f0c923e4488b1932d69678d3
  Ica825cf2af74f5624cf4091544bd24bb5482dbe7
  Id3ca7889ede30b54b7af73dd50653ca1a20d59aa

Bug: 26902605
Change-Id: Idcdc5bff133f13c1267f0ec0a75cc8cf1ddbda0d
(cherry picked from commit d122ee65b66b5b33d51302dabbaa0d6c84597549)
logd: enforce policy integrity 2016-02-16T20:54:54+00:00 Sami Tolvanen samitolvanen@google.com 2016-02-05T22:27:52+00:00 d122ee65b66b5b33d51302dabbaa0d6c84597549 If a SELinux policy change or a switch to permissive mode is detected on a user build, restart the device into safe mode, and keep it there until an OTA is applied or user data is wiped. This change deprecates the ro.logd.auditd property. Needs matching changes from I781c3059ea8d4fb2f0c923e4488b1932d69678d3 Ica825cf2af74f5624cf4091544bd24bb5482dbe7 Id3ca7889ede30b54b7af73dd50653ca1a20d59aa Bug: 26902605 Change-Id: Idcdc5bff133f13c1267f0ec0a75cc8cf1ddbda0d 
If a SELinux policy change or a switch to permissive mode is detected
on a user build, restart the device into safe mode, and keep it there
until an OTA is applied or user data is wiped.

This change deprecates the ro.logd.auditd property.

Needs matching changes from
  I781c3059ea8d4fb2f0c923e4488b1932d69678d3
  Ica825cf2af74f5624cf4091544bd24bb5482dbe7
  Id3ca7889ede30b54b7af73dd50653ca1a20d59aa

Bug: 26902605
Change-Id: Idcdc5bff133f13c1267f0ec0a75cc8cf1ddbda0d
logd: use ro.debuggable instead of ro.build.type 2016-02-10T18:23:03+00:00 Mark Salyzyn salyzyn@google.com 2016-02-09T23:49:29+00:00 d1f41d606b3b3e013014506bfa1cea09c15d2308 Change-Id: Ic644f1f78e68094f700834675f4acc63386a6b92 
Change-Id: Ic644f1f78e68094f700834675f4acc63386a6b92
logd: document ro.logd.size 2016-01-05T17:09:18+00:00 Mark Salyzyn salyzyn@google.com 2016-01-05T16:49:44+00:00 66607ebc0e451d239b7b15a8794cfd7bec992e6c Bad comment advise in LogBuffer.cpp results in partners failing to considering using ro.logd.size to set the platform buffer size default. NB: It is not good practice to increase the log buffer size to deal with logspam, as increases will result in logd scale issues getting closer to hitting the background cgroup cpu cap. Once we hit that cap, logd spirals, pruning old entries slower than the incoming log entries. logd.writer will take 100% cpu. Change-Id: If4a7a74f300d078eeaed0ffd3eb3fd77d1f9fe90 
Bad comment advise in LogBuffer.cpp results in partners failing to
considering using ro.logd.size to set the platform buffer size
default.

NB: It is not good practice to increase the log buffer size to deal
with logspam, as increases will result in logd scale issues getting
closer to hitting the background cgroup cpu cap. Once we hit that
cap, logd spirals, pruning old entries slower than the incoming log
entries. logd.writer will take 100% cpu.

Change-Id: If4a7a74f300d078eeaed0ffd3eb3fd77d1f9fe90