From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp89.ord1c.emailsrvr.com (smtp89.ord1c.emailsrvr.com [108.166.43.89]) by dpdk.org (Postfix) with ESMTP id 7BA3737B2 for ; Fri, 22 Apr 2016 10:51:53 +0200 (CEST) Received: from smtp12.relay.ord1c.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp12.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id E89CF3800CC for ; Fri, 22 Apr 2016 04:51:52 -0400 (EDT) X-Auth-ID: padam.singh@inventum.net Received: by smtp12.relay.ord1c.emailsrvr.com (Authenticated sender: padam.singh-AT-inventum.net) with ESMTPSA id 463FD3800B5 for ; Fri, 22 Apr 2016 04:51:51 -0400 (EDT) X-Sender-Id: padam.singh@inventum.net Received: from [172.16.1.231] ([UNAVAILABLE]. [103.25.205.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:25 (trex/5.5.4); Fri, 22 Apr 2016 04:51:52 -0400 From: Padam Jeet Singh Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: <4A51DD33-CDB5-4688-90EA-22087C24B729@inventum.net> Date: Fri, 22 Apr 2016 14:21:47 +0530 To: dev@dpdk.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) Subject: [dpdk-dev] Segmentation fault in ip_frag_find X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2016 08:51:53 -0000 Hello, We are using the DPDK framework and testing the IP reassembly code. While reassembly is working fine, the application segfaults with the = following (partially shown) stack trace. The segfault is not entirely = reproducible - it happens quite randomly. Program terminated with signal 11, Segmentation fault. #0 0x00000000004b3408 in ip_frag_find () (gdb) bt #0 0x00000000004b3408 in ip_frag_find () #1 0x00000000004b0cde in rte_ipv4_frag_reassemble_packet () All the required checks before we call this function: 1. Death Row is initialised, and not null. 2. The reassemble table is initialised and not null. 3. Protect the reassembly code with a spin lock, so it=E2=80=99s not a = thread issue. 4. Free the death row by calling rte_ip_frag_free_death_row post the = reassembly call within the spin lock itself. 5. At transmit time, the reassembled packet is fragmented again to match = the outbound MTU. Version of DPDK is 1.7, however I have checked the git tree and not = found any functional changes to till the stable version. Any inputs/ideas on how the issue can be fixed? Thanks, Padam=