diff options
author | Alyssa Ross <hi@alyssa.is> | 2020-06-05 23:47:57 +0000 |
---|---|---|
committer | Alyssa Ross <hi@alyssa.is> | 2020-06-14 11:24:27 +0000 |
commit | 1e318da5b57c12f67bed3b528100dbe4ec287ac5 (patch) | |
tree | 2c5b2e2011796a9e71fbc5adcf1a85b33b04051c /seccomp/x86_64/9p_device.policy | |
parent | 28d9682698d287d14cbe67a0ed7acc1427add320 (diff) | |
download | crosvm-1e318da5b57c12f67bed3b528100dbe4ec287ac5.tar crosvm-1e318da5b57c12f67bed3b528100dbe4ec287ac5.tar.gz crosvm-1e318da5b57c12f67bed3b528100dbe4ec287ac5.tar.bz2 crosvm-1e318da5b57c12f67bed3b528100dbe4ec287ac5.tar.lz crosvm-1e318da5b57c12f67bed3b528100dbe4ec287ac5.tar.xz crosvm-1e318da5b57c12f67bed3b528100dbe4ec287ac5.tar.zst crosvm-1e318da5b57c12f67bed3b528100dbe4ec287ac5.zip |
seccomp: allow getdents64 if getdents is allowed
This fixes a crash where crosvm would crash if run on x86_64 with --shared-dir when running ls in the shared directory. I suspect whether getdents or getdents64 is used depends on the host libc, so allow both of them. I suspect upstream's libc uses getdents, and that's why they haven't fixed the problem. Message-Id: <20200605234757.28848-1-hi@alyssa.is>
Diffstat (limited to 'seccomp/x86_64/9p_device.policy')
-rw-r--r-- | seccomp/x86_64/9p_device.policy | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/seccomp/x86_64/9p_device.policy b/seccomp/x86_64/9p_device.policy index 114ea11..271d244 100644 --- a/seccomp/x86_64/9p_device.policy +++ b/seccomp/x86_64/9p_device.policy @@ -18,6 +18,7 @@ unlink: 1 rename: 1 pread64: 1 getdents: 1 +getdents64: 1 mkdir: 1 rmdir: 1 fsync: 1 |