summary refs log tree commit diff
path: root/src/plugin/mod.rs
diff options
context:
space:
mode:
authorZach Reizner <zachr@google.com>2019-03-12 10:26:50 -0700
committerchrome-bot <chrome-bot@chromium.org>2019-03-14 20:53:40 -0700
commit4725a399f794709c97bb62f4e1cd8a5b6bfafd5c (patch)
tree361336f22da14aa4ee4acffb129bc78c8800709a /src/plugin/mod.rs
parente00faed85c496403b6bf4fa08292ee90291e9c1d (diff)
downloadcrosvm-4725a399f794709c97bb62f4e1cd8a5b6bfafd5c.tar
crosvm-4725a399f794709c97bb62f4e1cd8a5b6bfafd5c.tar.gz
crosvm-4725a399f794709c97bb62f4e1cd8a5b6bfafd5c.tar.bz2
crosvm-4725a399f794709c97bb62f4e1cd8a5b6bfafd5c.tar.lz
crosvm-4725a399f794709c97bb62f4e1cd8a5b6bfafd5c.tar.xz
crosvm-4725a399f794709c97bb62f4e1cd8a5b6bfafd5c.tar.zst
crosvm-4725a399f794709c97bb62f4e1cd8a5b6bfafd5c.zip
seccomp: tpm: remove fseek syscall from policy
There is no such syscall as fseek as far as I can tell. There is lseek,
which would be how fseek is implemented in libc, and it is already
included in the policy.

BUG=chromium:936633
TEST=parse_seccomp_policy seccomp/x86_64/tpm_device.policy

Change-Id: Ifb891395d7447d8b81cb1b17af18c49e5d5fc96f
Reviewed-on: https://chromium-review.googlesource.com/1518490
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Diffstat (limited to 'src/plugin/mod.rs')
0 files changed, 0 insertions, 0 deletions