summaryrefslogtreecommitdiffstats
path: root/sandbox/linux/seccomp/madvise.cc
diff options
context:
space:
mode:
authormarkus@chromium.org <markus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-11-07 06:09:38 +0000
committermarkus@chromium.org <markus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-11-07 06:09:38 +0000
commita9c54a176540e3a8173d72a1794cac3855bc9ce0 (patch)
tree7d316f2558c7e4f923d0c97ef45c4ed08b59cb45 /sandbox/linux/seccomp/madvise.cc
parent282f4d24b40587c701ede40b014035ceffc9a3ea (diff)
downloadchromium_src-a9c54a176540e3a8173d72a1794cac3855bc9ce0.zip
chromium_src-a9c54a176540e3a8173d72a1794cac3855bc9ce0.tar.gz
chromium_src-a9c54a176540e3a8173d72a1794cac3855bc9ce0.tar.bz2
Allow the seccomp sandbox to be enabled, even if the suid sandbox has
already put a chroot() jail around it. The only tricky part is access to /proc/self/maps, but we can safely pass in an open file descriptor. BUG=26527 Review URL: http://codereview.chromium.org/371047 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31372 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sandbox/linux/seccomp/madvise.cc')
-rw-r--r--sandbox/linux/seccomp/madvise.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/sandbox/linux/seccomp/madvise.cc b/sandbox/linux/seccomp/madvise.cc
index 738da7f..92344df 100644
--- a/sandbox/linux/seccomp/madvise.cc
+++ b/sandbox/linux/seccomp/madvise.cc
@@ -26,7 +26,7 @@ int Sandbox::sandbox_madvise(void* start, size_t length, int advice) {
return static_cast<int>(rc);
}
-bool Sandbox::process_madvise(int parentProc, int sandboxFd, int threadFdPub,
+bool Sandbox::process_madvise(int parentMapsFd, int sandboxFd, int threadFdPub,
int threadFd, SecureMem::Args* mem) {
// Read request
MAdvise madvise_req;