Skip to content
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

kernel-5.10,5.15: Backport of upstream commit bpf: Adjust insufficient default bpf_jit_limit #3002

Merged
merged 1 commit into from
Apr 11, 2023

Conversation

foersleo
Copy link
Contributor

Issue number: -

Description of changes:

Backport upstream commit to adjust the memory size available to the bpf jit. While we will pick this patch up in due curse once we update kernel to 5.10.177 and 5.15.105, pick them up for now to ensure our next release has this one fixed.

Testing done:

Did some simple build testing. Given the nature of this patch, relaxing the memory restrictions for the bpf jit, I do not suspect any side effects from this.

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

default bpf_jit_limit`

Backport upstream commit to adjust the memory size available to the bpf
jit. While we will pick this patch up in due curse once we update kernel
to 5.10.177 and 5.15.105, pick them up for now to ensure our next
release has this one fixed.

Signed-off-by: Leonard Foerster <foersleo@amazon.com>
Copy link
Contributor

@stmcginnis stmcginnis left a comment

Choose a reason for hiding this comment

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

Jobs are happy and looks good to me.

Copy link
Contributor

@zmrow zmrow left a comment

Choose a reason for hiding this comment

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

🫕

@foersleo foersleo merged commit fcd98c0 into bottlerocket-os:develop Apr 11, 2023
37 checks passed
@foersleo foersleo deleted the backport_bpf_jit branch April 12, 2023 06:05
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.

None yet

5 participants