Project

General

Profile

Actions

Bug #1101

closed

Segmentation in AppLayerParserGetTxCnt

Added by Duarte Silva over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

Detected a segmentation fault in AppLayerParserGetTxCnt. One interesting fact, is the CPU usage on the flow manager thread, don't know if it could have impact or not. I can reproduce it consistently by replaying a packet dump (replaying at ~400Mbps).

Suricata has been compiled without optimizations.


Files

thread-dump.txt (18.3 KB) thread-dump.txt Back trace for the various threads Duarte Silva, 02/07/2014 10:43 AM
buildinfo.txt (2.11 KB) buildinfo.txt Suricata build information Duarte Silva, 02/07/2014 10:44 AM
top.txt (702 Bytes) top.txt CPU usage while processing replayed packed capture Duarte Silva, 02/07/2014 10:44 AM
flow-dump-thread-2.txt (7.63 KB) flow-dump-thread-2.txt Thread were the segmentation fault happened Duarte Silva, 02/07/2014 12:10 PM
flow-dump-thread-4.txt (7.29 KB) flow-dump-thread-4.txt Thread that is processing the same flow Duarte Silva, 02/07/2014 12:10 PM
thread-dump-2.txt (18.2 KB) thread-dump-2.txt Second back trace for all threads Duarte Silva, 02/07/2014 12:10 PM
suricata.yaml (49 KB) suricata.yaml Current Suricata configuration Duarte Silva, 02/07/2014 12:10 PM
Actions #1

Updated by Duarte Silva over 7 years ago

Had to reproduced the segmentation fault in order to able to dump the flow and packet variables (also learned how to save core dumps from gdb ;)).

Actions #2

Updated by Victor Julien over 7 years ago

Are you able to share the packet dump privately?

Actions #3

Updated by Victor Julien over 7 years ago

  • Status changed from New to Assigned
  • Assignee set to Victor Julien
  • Target version set to 2.0.1rc1
Actions #4

Updated by Victor Julien over 7 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF