Project

General

Profile

Actions

Bug #6584

closed

SCTIME_ADD_SECS() macro zeros out ts.usec part

Added by Stephen Donnelly about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Target version:
Affected Versions:
Effort:
low
Difficulty:
low
Label:
Beginner, C

Description

The SCTIME_* macros may need some review.

Napatech's PR https://github.com/OISF/suricata/pull/9833 fixes SCTIME_ADD_USECS(), however there are other issues. Currently the SCTIME_ADD_SECS(ts, s) macro adds s seconds to ts.secs and clears ts.usecs.

I would argue that SCTIME_ADD_SECS(ts, s) should return ts.usecs unmodified, otherwise one integer second is not added to ts.

E.g. currently ts.secs = 10, ts.usecs = 999999, s = 1, results in ts.secs = 11, ts.usecs = 0. Only 1 microsecond is added to ts.

This bug could affect various time related operations such as fragment reassembly, detection engine thresholds etc.


Subtasks 1 (0 open1 closed)

Bug #6596: SCTIME_ADD_SECS() macro zeros out ts.usec part (7.0.x backport)ClosedJeff LucovskyActions

Related issues 1 (0 open1 closed)

Related to Suricata - Bug #6585: SCTIME_FROM_TIMESPEC() creates incorrect timestampsClosedStephen DonnellyActions
Actions #1

Updated by Victor Julien about 1 year ago

  • Related to Bug #6585: SCTIME_FROM_TIMESPEC() creates incorrect timestamps added
Actions #2

Updated by Victor Julien about 1 year ago

  • Target version changed from TBD to 7.0.3
Actions #3

Updated by Victor Julien about 1 year ago

  • Target version changed from 7.0.3 to 8.0.0-beta1
Actions #4

Updated by Jeff Lucovsky about 1 year ago

  • Status changed from New to In Review
  • Assignee changed from OISF Dev to Jeff Lucovsky
Actions #6

Updated by OISF Ticketbot about 1 year ago

  • Subtask #6596 added
Actions #7

Updated by OISF Ticketbot about 1 year ago

  • Label deleted (Needs backport to 7.0)
Actions #8

Updated by Victor Julien about 1 year ago

  • Assignee changed from Jeff Lucovsky to Stephen Donnelly
Actions #9

Updated by Jeff Lucovsky about 1 year ago

  • Status changed from In Review to Resolved
Actions #10

Updated by Jeff Lucovsky about 1 year ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF