Page MenuHomeFreeBSD

capsicum-test: Update for O_BENEATH removal
ClosedPublic

Authored by arichardson on Mar 2 2021, 6:26 PM.
Tags
None
Referenced Files
F167421722: D29016.id85645.diff
Fri, Aug 21, 3:48 PM
Unknown Object (File)
Thu, Aug 20, 6:06 PM
Unknown Object (File)
Thu, Aug 20, 9:15 AM
Unknown Object (File)
Wed, Aug 19, 1:23 AM
Unknown Object (File)
Tue, Aug 18, 8:10 PM
Unknown Object (File)
Wed, Aug 12, 9:27 PM
Unknown Object (File)
Sun, Aug 9, 11:45 AM
Unknown Object (File)
Sun, Aug 9, 11:44 AM
Subscribers

Details

Summary

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.

Test Plan

/usr/tests/sys/capsicum/capsicum-test -u 977 passes and runs the O_RESOLVE_BENEATH tests.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Mar 2 2021, 6:29 PM
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.