Multicast Stack Fix #15
Open
Conversation
This file contains 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
Currently the multicast stack is seriously broken by incorrect dynamic memory allocation of multicast vif arrays. This commit fixes this issue. Fixes: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248512#add_comment Fixes: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246629 Other references: https://forum.opnsense.org/index.php?topic=18490.0 https://redmine.pfsense.org/issues/10558#change-46850
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.
Currently the multicast stack in stable is seriously broken by incorrect dynamic memory allocation of multicast vif arrays. This commit fixes this issue.
Fixes: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248512#add_comment
Fixes: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246629
Other references:
https://forum.opnsense.org/index.php?topic=18490.0
https://redmine.pfsense.org/issues/10558#change-46850