[Oisf-devel] Segmentation fault on the latest Suricata beta

[Victor Julien]

On 02/07/2014 06:37 PM, Duarte Silva wrote:
> On Friday 07 February 2014 18:23:55 Victor Julien wrote:
>> On 02/07/2014 05:56 PM, Duarte Silva wrote:
>>> Hi Victor,
>>>
>>> I have come to a conclusion about this. The fact that Suricata is compiled
>>> with stack protection and position independent code, doesn't seem to have
>>> anything to do with the issue in hand.
>>>
>>> Actually, that specific segmentation fault did not happened again (another
>>> one did, I didn't compare back traces correctly :/).
>>>
>>> Anyway, the new segmentation fault still happens on master, at least, up
>>> to
>>> commit 3967bd5517e7ab57fd82d7ce9b70dac16057b8f7. Issue opened at [1].
>>
>> This is very interesting. It looks like 2 packet processing threads have
>> the same flow. This is not supposed to happen.
>>
>> You are using workers, correct?
> 
> Yes, I'm.
>  
>> In gdb, can you do:
>>
>> thread 4
>> frame 4
>> print *p
>> print *p->flow
>>
>> and
>>
>> thread 5
>> frame 5
>> print *p
>> print *p->flow
> 
> I terminated the gdb session, I will reproduce the issue and hopefully the 
> condition repeats it self (I really need to start saving core dumps :D)
> 

Ah, too bad.

In af-packet, are you using the cluster flow setting? What kernel
version, NIC and driver do you have?

-- 
---------------------------------------------
Victor Julien
http://www.inliniac.net/
PGP: http://www.inliniac.net/victorjulien.asc
---------------------------------------------