[Oisf-devel] [COMMIT] OISF branch, master, updated. suricata-1.4-165-g93e7304

noreply at openinfosecfoundation.org noreply at openinfosecfoundation.org
Wed May 15 10:54:14 UTC 2013

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "OISF".

The branch, master has been updated
       via  93e73041171a294063061648e880ec898a2da828 (commit)
       via  699d9e01f12f4a6e88af2e61a36bb9bf46c4ee9a (commit)
      from  71c22ddfeefd4fdea88eed9a5d310d3d0169a978 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 93e73041171a294063061648e880ec898a2da828
Author: Ken Steele <ken at tilera.com>
Date:   Tue May 14 15:38:00 2013 -0400

    Preserve PKT_ALLOC flag inside PACKET_RECYCLE().
    The PKT_ALLOC flag was being cleared by PACKET_RECYCLE(), which could
    then result in a packet being pushed back to the Packet ring buffer

commit 699d9e01f12f4a6e88af2e61a36bb9bf46c4ee9a
Author: Ken Steele <ken at tilera.com>
Date:   Tue May 14 15:00:21 2013 -0400

    Move memset() out of PACKET_INITIALIZE()
    The memset() inside PACKET_INITIALIZE() is redundant in some cases and
    it is cleaner to do as part of the memory allocation. This simplifies
    changes for integrating Tilera mPIPE support because the size of memory
    cleared in that case is different from SIZE_OF_PACKET.
    For the cases where Packets are directly allocated and then call
    PACKET_INITIALIZE() without memset() first, this patch adds memset() calls.
    A further change would use GetPacketFromAlloc() directly.


Summary of changes:
 src/decode-ipv4.c     |    3 +++
 src/decode.c          |    1 +
 src/decode.h          |    6 ++----
 src/stream-tcp.c      |    2 ++
 src/tmqh-packetpool.c |    1 +
 5 files changed, 9 insertions(+), 4 deletions(-)


More information about the Oisf-devel mailing list