Update the tests to check O_RESOLVE_BENEATH instead.
If this looks reasonable, I'll try to upstream this change.
This keeps a compat fallback for O_BENEATH since the Linux port still
has/had O_BENEATH with "no .., no absolute paths" semantics.
Details
Details
/usr/tests/sys/capsicum/capsicum-test -u 977 passes and runs the O_RESOLVE_BENEATH tests.
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
No Lint Coverage - Unit
No Test Coverage - Build Status
Buildable 37507 Build 34396: arc lint + arc unit
Event Timeline
| contrib/capsicum-test/openat.cc | ||
|---|---|---|
| 357 | This is weird, because if you redefine O_RESOLVE_BENEATH as O_BENEATH, this could succeed (depending on the cwd). | |
| contrib/capsicum-test/openat.cc | ||
|---|---|---|
| 357 | I think there could be other interesting errors if cwd == /. I guess the testsuite should check that the cwd is not inside / or /etc. | |