Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ASan does not play well with the seccomp sandbox on Linux #90

Closed
ramosian-glider opened this issue Aug 31, 2015 · 2 comments
Closed

ASan does not play well with the seccomp sandbox on Linux #90

ramosian-glider opened this issue Aug 31, 2015 · 2 comments

Comments

@ramosian-glider
Copy link
Member

Originally reported on Google Code with ID 90

Seccomp sandbox (http://code.google.com/p/seccompsandbox/wiki/overview) restricts the
list of syscalls allowed for a certain thread to execute (see e.g. https://src.chromium.org/viewvc/chrome/trunk/src/content/common/sandbox_init_linux.cc?view=markup)

This may become a problem if ASan calls a syscall that's forbidden in the current process,
so it may be a good idea to get rid of the unnecessary syscalls in our runtime. open()
is the first candidate.

Reported by ramosian.glider on 2012-07-18 12:42:22

@ramosian-glider
Copy link
Member Author

Reported by ramosian.glider on 2013-01-14 14:13:36

@ramosian-glider
Copy link
Member Author

Adding Project:AddressSanitizer as part of GitHub migration.

Reported by ramosian.glider on 2015-07-30 09:12:59

  • Labels added: ProjectAddressSanitizer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant