-
Notifications
You must be signed in to change notification settings - Fork 4
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
wip: new: role drivers test #84
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Federico Di Pierro <nierro92@gmail.com>
…_test and scap-open. Signed-off-by: Federico Di Pierro <nierro92@gmail.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: FedeDP The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Federico Di Pierro <nierro92@gmail.com>
250281d
to
2be54f4
Compare
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
This PR adds a new drivers_test role to run
drivers_test
executable on each VM.It requires the binary to be built on each VM because the drivers tests are bound to the running kernel.
In a simple test i took on
amazonlinux2022-5.15
, we have multiple failures:clone3
fail with EINVAL, most probably because the kernel was built withoutCONFIG_PID_NS
option:(from https://man7.org/linux/man-pages/man2/clone.2.html).
execveX_not_upperlayer
andexecveX_upperlayer_success
fail because they cannot mount overlayFSprocess_vm_readvX_failure
fails because apparentlyprocess_vm_readv
syscall did not failI think all of these are addressable (most probably we just need to tweak the kernel config a bit, except for
process_vm_readvX_failure
that must be checked on its own)