dnsdist-1.7.x: Properly use eBPF when the DynBlock is not set #11550
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When the DynBlock rule does not set a specific action we use the default one, set with `setDynBlocksAction()`, so we should follow the same logic when determining whether to insert an eBPF block. (cherry picked from commit 8742251)
rgacogne
force-pushed
the
ddist17-bpf-block-action
branch
from
534a1a7 to
dcddd2f
Compare
|
Rebased to fix the jinja2 failure. |
chbruyand
approved these changes
Apr 22, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Short description
When the DynBlock rule does not set a specific action we use the default one, set with
setDynBlocksAction(), so we should follow the same logic when determining whether to insert an eBPF block.(cherry picked from commit 8742251)
Backport of #11544 to rel/dnsdist-1.7.x.
Checklist
I have: