summaryrefslogtreecommitdiff
path: root/trusty/coverage/coverage.cpp
diff options
context:
space:
mode:
authorBen Zhang <benzh@chromium.org>2015-01-20 17:26:31 -0800
committerChromeOS Commit Bot <chromeos-commit-bot@chromium.org>2015-01-22 05:13:33 +0000
commit1c5533d4cd99f19ec8a37aaa841caeba76f7005c (patch)
tree81edf49d356e7bb8ea11a7adcfdb7248d2684440 /trusty/coverage/coverage.cpp
parent859ee45cd2d9feb5e937c0c06f9e6c230979136e (diff)
crash-reporter: add a sanity check for kernel dmesg records
On some devices, after a cold boot, a junk pstore record /dev/pstore/dmesg-ramoops-0 is created which is just a chunk of uninitialized memory containing random bits, and it's not the result of a kernel crash. The sanity check scans for the dmesg log level pattern to avoid creating junk .kcrash files. BUG=chromium:443764 TEST=platform_KernelErrorPaths with 3.8 and 3.14 kernel; check no kcrash file is created for random binary ramoops dump on stumpy. Change-Id: I83041436cd8e5e0c7c0015c529f462032ce82f30 Signed-off-by: Ben Zhang <benzh@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/242147 Reviewed-by: Olof Johansson <olofj@chromium.org> Reviewed-by: Grant Grundler <grundler@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org>
Diffstat (limited to 'trusty/coverage/coverage.cpp')
0 files changed, 0 insertions, 0 deletions