summary refs log tree commit diff
path: root/seccomp
diff options
context:
space:
mode:
authorZach Reizner <zachr@google.com>2018-04-03 20:47:21 -0700
committerchrome-bot <chrome-bot@chromium.org>2018-04-04 22:53:21 -0700
commit043ddc5c0d281e027f23db049788db29f2fedbe6 (patch)
tree21823b9fd3039a5601698b565040f12355bb7281 /seccomp
parenta7fae252b05b617fd27f58b9bba8122d18154ccb (diff)
downloadcrosvm-043ddc5c0d281e027f23db049788db29f2fedbe6.tar
crosvm-043ddc5c0d281e027f23db049788db29f2fedbe6.tar.gz
crosvm-043ddc5c0d281e027f23db049788db29f2fedbe6.tar.bz2
crosvm-043ddc5c0d281e027f23db049788db29f2fedbe6.tar.lz
crosvm-043ddc5c0d281e027f23db049788db29f2fedbe6.tar.xz
crosvm-043ddc5c0d281e027f23db049788db29f2fedbe6.tar.zst
crosvm-043ddc5c0d281e027f23db049788db29f2fedbe6.zip
crosvm: enable seccomp logging in debug builds
This will be useful for diagnosing crosvm crashes which are most often
caused by seccomp killing a device process.

TEST=delete a seccomp filter, run crosvm, check for blocked syscall in
     /var/log/messages
BUG=None

Change-Id: I1e01a0794f0349e6ad9b101eb2e32320f60b1283
Reviewed-on: https://chromium-review.googlesource.com/994737
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
Diffstat (limited to 'seccomp')
0 files changed, 0 insertions, 0 deletions