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

detect/port: bug-6843 - v2 #10602

Closed
wants to merge 1 commit into from
Closed

Conversation

inashivb
Copy link
Member

@inashivb inashivb commented Mar 9, 2024

Runtime on this PR:

real	0m28.604s
user	0m28.202s
sys	0m0.352s

vs master:

real	0m28.551s
user	0m28.126s
sys	0m0.364s

Link to redmine ticket: https://redmine.openinfosecfoundation.org/issues/6843

SV_BRANCH=OISF/suricata-verify#1692

Changes since v1:

  • rebased on top of latest master

If a port point is single but later on also a part of a range, it ends
up only creating the port groups for single points and not the range.
Fix it by adding the port next to current single one to unique points
and marking it a range port.

Bug 6843
@inashivb inashivb changed the title detect/port: handle single port that is range too detect/port: bug-6843 - v2 Mar 9, 2024
Copy link

codecov bot commented Mar 9, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.72%. Comparing base (2d6708f) to head (8b0a6f2).

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #10602       +/-   ##
===========================================
+ Coverage   62.20%   82.72%   +20.51%     
===========================================
  Files         924      924               
  Lines      247158   247452      +294     
===========================================
+ Hits       153741   204698    +50957     
+ Misses      93417    42754    -50663     
Flag Coverage Δ
fuzzcorpus 64.03% <100.00%> (?)
suricata-verify 61.87% <100.00%> (?)
unittests 62.20% <57.14%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

@inashivb inashivb marked this pull request as ready for review March 9, 2024 07:54
@suricata-qa
Copy link

Information: QA ran without warnings.

Pipeline 19160

@victorjulien victorjulien added this to the 8.0 milestone Mar 9, 2024
@victorjulien
Copy link
Member

Merged in #10608, thanks!

@inashivb inashivb deleted the bug-6843/v2 branch March 11, 2024 04:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants