8000 Bugfix/rodata err 419 by AlonZivony · Pull Request #2447 · aquasecurity/tracee · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Bugfix/rodata err 419 #2447

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
merged 1 commit into from
Dec 7, 2022

Conversation

AlonZivony
Copy link
Contributor
@AlonZivony AlonZivony commented Dec 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)

In old kernels (like focal 4.19) it seems that using raw strings put
those strings in .rodata segment, which is unavailable in eBPF
programs.
To solve it, the usage was change to put it on the stack.

Fixes: #2448

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?

Tested when used on top of reduced size sched_process_exec event, to see if it crashes or not (the event size crashes before it).

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 bugfix/rodata-err-419 branch 2 times, most recently from 2f2e80b to 64a65c8 Compare December 7, 2022 14:08
@AlonZivony AlonZivony requested a review from yanivagman December 7, 2022 14:09
In old kernels (like focal 4.19) it seems that using raw strings put
those strings in .rodata segment, which is unavailable in eBPF
programs.
To solve it, the usage was change to put it on the stack.
@AlonZivony AlonZivony force-pushed the bugfix/rodata-err-419 branch from 64a65c8 to b9cbdf3 Compare December 7, 2022 14:10
@AlonZivony AlonZivony marked this pull request as ready for review December 7, 2022 14:11
Copy link
Collaborator
@yanivagman yanivagman left a comment

Choose a reason for hiding this comment

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

LGTM

@yanivagman yanivagman merged commit f9aca90 into aquasecurity:main Dec 7, 2022
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.

[BUG] Error because of .rodata reference in kernel 4.19
2 participants
0