tree 7bcc3f567dc9282501d2b69f5343027c18a0ff2f
parent 219ef270a6907f4310bc1640ac404707c5a6ecc4
author Mark Salyzyn <salyzyn@google.com> 1492458372 -0700
committer Mark Salyzyn <salyzyn@google.com> 1492525481 -0700

logd: iterator corruption paranoia

(cherry pick from commit 3614a0c5d4aec84fbc5f6cbf1e919e8b3825b818)

Add checking for impossible(tm) scenarios within LogBuffer::flushTo:

1) When iterating through the log entries, check if the iterator
   returns two identical element references and break out of the loop.
2) Cap the maximum number of log entries we will skip while holding
   the iterator lock at 4194304, break out of the loop.

We print a message to the kernel logs if we hit these cases.

ToDo: Remove this paranoia at some future date.

Test: gTest liblog-unit-tests logcat-unit-tests and logd-unit-tests
Bug: 37378309
Change-Id: I789594649db14093238828b9f6d1daeca8b780c2