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

Next/41x/20191129/v10 #4414

Merged
merged 20 commits into from Dec 4, 2019

Conversation

victorjulien
Copy link
Member

#4413 except the fatal error is a warning now.

PRScript output (if applicable):
Passed.

jasonish and others added 20 commits November 28, 2019 12:00
If a protocol does not support TxDetectFlags, don't try to use them.

The consequence of trying to use them was that a TX would never be
considered done, and it would never be freed. This would lead to excessive
memory use and performance problems due to walking an ever increasing
list.

(cherry picked from commit ab471c3)
(cherry picked from commit b1beb76)
Define a TxDetectFlag type and macros to generating C
bindings for getting and settings the tx detect
flags.

(cherry picked from commit 8a232be)

VJ: std::os::raw::c_void to libc::c_void
(cherry picked from commit 21f014f)
(cherry picked from commit cb62c8d)
(cherry picked from commit 706558d)
Check that both are set or unset.

(cherry picked from commit ba3a2c3)
Example of using GitHub actions to perform builds across
CentOS, Ubuntu, Debian and the latest Fedora.

(cherry picked from commit 3887f8d)
Add method to check if a parser for an app-layer protocol
supports tx detect flags.

This is a bit of a hack for now as where we need to run
this check from we do not have the IP protocol.
When registing a detection engine, check that the app-layer
protocol supports tx detect flags.

This is a code implementation error that should be resolved
during development.

VJ: made this a warning as we're updating an older stable
branch.
Copy link
Member

@jasonish jasonish left a comment

Choose a reason for hiding this comment

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

Was just about to approve the previous one, but then saw this...

@victorjulien victorjulien merged commit 655a6a3 into OISF:master-4.1.x Dec 4, 2019
@victorjulien victorjulien deleted the next/41x/20191129/v10 branch December 10, 2019 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants