8000 pkg/ebpf: add syscalls arguments to security_file_mprotect by AlonZivony · Pull Request #2335 · aquasecurity/tracee · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

pkg/ebpf: add syscalls arguments to security_file_mprotect #2335

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

Merged

Conversation

AlonZivony
Copy link
Contributor
@AlonZivony AlonZivony commented Nov 7, 2022

Initial Checklist

  • There is an issue describing the need for this PR.
  • Git log contains summary of the change.
  • Git log contains motivation and context of the change.
  • If part of an EPIC, PR git log contains EPIC number.
  • If part of an EPIC, PR was added to EPIC description.

Description (git log)

Add missing information in the security_file_mprotect, like address and len of operation.
Add support to the pkey_mprotect syscall too.

Fixes: #2334

Type of change

  • Bug fix (non-breaking change fixing an issue, preferable).
  • Quick fix (minor non-breaking change requiring no issue, use with care)
  • Code refactor (code improvement and/or code removal)
  • New feature (non-breaking change adding functionality).
  • Breaking change (cause existing functionality not to work as expected).

How Has This Been Tested?

Ran the event with the mprotect and pkey_mprotect to check that the event works well.

Final Checklist:

Pick "Bug Fix" or "Feature", delete the other and mark appropriate checks.

  • I have made corresponding changes to the documentation.
  • My code follows the style guidelines (C and Go) of this project.
  • I have performed a self-review of my own code.
  • I have commented all functions/methods created explaining what they do.
  • I have commented my code, particularly in hard-to-understand areas.
  • My changes generate no new warnings.
  • I have added tests that prove my fix, or feature, is effective.
  • New and existing unit tests pass locally with my changes.
  • Any dependent changes have been merged and published before.

Git Log Checklist:

My commits logs have:

  • Subject starts with "subsystem|file: description".
  • Do not end the subject line with a period.
  • Limit the subject line to 50 characters.
  • Separate subject from body with a blank line.
  • Use the imperative mood in the subject line.
  • Wrap the body at 72 characters.
  • Use the body to explain what and why instead of how.

@AlonZivony AlonZivony force-pushed the feature/add-mprotect-args-to-lsm branch 2 times, most recently from 39aab1c to ad25054 Compare November 7, 2022 12:39
Add missing information in the security_file_mprotect, like address
and len of operation.
Add support to the `pkey_mprotect` syscall too.
@AlonZivony AlonZivony force-pushed the feature/add-mprotect-args-to-lsm branch from ad25054 to aff47f1 Compare November 8, 2022 13:27
@rafaeldtinoco rafaeldtinoco self-requested a review November 9, 2022 12:42
Copy link
Contributor
@rafaeldtinoco rafaeldtinoco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for documenting the event Alon!

@rafaeldtinoco rafaeldtinoco merged commit d30ef65 into aquasecurity:main Nov 9, 2022
@AlonZivony AlonZivony deleted the feature/add-mprotect-args-to-lsm branch November 9, 2022 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEAT] Add mprotect args to security_file_mprotect
2 participants
0