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 v7 #1454

Merged
merged 11 commits into from
Apr 30, 2015
Merged

Next v7 #1454

merged 11 commits into from
Apr 30, 2015

Conversation

inliniac
Copy link
Contributor

victorjulien and others added 11 commits April 30, 2015 12:53
Coverity:
** CID 1296115:  Program hangs  (ORDER_REVERSAL)
/src/tm-threads.c: 1670 in TmThreadClearThreadsFamily()

The problem is with the by default unused '%m' output parameter.
To get the thread vars it takes the tv_root_lock. This may already
be locked by the calling thread. Also, it could lead to a case of
wrong lock order between the tv_root_lock and the thread_store_lock.

Very unlikely to happen though.

As the %m param isn't really used (by default) this patch just
disables it.
Switch statement would contain NOALERT even though this was
unreachable.
Fix poor int handling breaking sorts of profiling on long runs
where the numbers could get really big.
A typo was causing some freeing tasks not to be executed.
Implement LINKTYPE_NULL for pcap live and pcap file.

From: http://www.tcpdump.org/linktypes.html

"BSD loopback encapsulation; the link layer header is a 4-byte field,
 in host byte order, containing a PF_ value from socket.h for the
 network-layer protocol of the packet.

 Note that ``host byte order'' is the byte order of the machine on
 which the packets are captured, and the PF_ values are for the OS
 of the machine on which the packets are captured; if a live capture
 is being done, ``host byte order'' is the byte order of the machine
 capturing the packets, and the PF_ values are those of the OS of
 the machine capturing the packets, but if a ``savefile'' is being
 read, the byte order and PF_ values are not necessarily those of
 the machine reading the capture file."

Feature ticket #1445
@inliniac inliniac merged commit 04ccfda into master Apr 30, 2015
@inliniac inliniac deleted the next-v7 branch May 7, 2015 09:43
zrasmor added a commit to zrasmor/suricata that referenced this pull request May 24, 2015
zrasmor added a commit to zrasmor/suricata that referenced this pull request Jun 3, 2015
zrasmor added a commit to zrasmor/suricata that referenced this pull request Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants