From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 60A1CA0471 for ; Tue, 13 Aug 2019 05:05:21 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D74AD8F96; Tue, 13 Aug 2019 05:05:19 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id 126C25681 for ; Tue, 13 Aug 2019 05:05:18 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id CD91EA10D6; Tue, 13 Aug 2019 05:05:17 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Tue, 13 Aug 2019 03:05:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 17.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: abhijeet080808@gmail.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 338] IP Reassembly with more 4 packets Segfault X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D338 Bug ID: 338 Summary: IP Reassembly with more 4 packets Segfault Product: DPDK Version: 17.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: Normal Component: core Assignee: dev@dpdk.org Reporter: abhijeet080808@gmail.com Target Milestone: --- I have looked at previous mails on this mailing list and also elsewhere on Google and could not find any information related to this. Whenever I have to reassemble a valid IP packet with more than 4 fragments,= I see a crash. Stack trace below. I assume the number 4 comes from RTE_LIBRTE_IP_FRAG_MAX_FRAG. To trigger this, I sent a fragmented IP packet via - ping -s 6000 (gdb) bt #0 ip_frag_lookup (tbl=3Dtbl@entry=3D0x7fff7a32ce80, key=3Dkey@entry=3D0x7= ffff6eeee10, tms=3Dtms@entry=3D2602613353715115, free=3Dfree@entry=3D0x7ffff6eeedb8,=20 stale=3Dstale@entry=3D0x7ffff6eeedc0) at /usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/ip_frag_intern= al.c:379 #1 0x00007ffff7c021f6 in ip_frag_find (tbl=3Dtbl@entry=3D0x7fff7a32ce80, dr=3Ddr@entry=3D0x7fff7a32c900, key=3Dkey@entry=3D0x7ffff6eeee10, tms=3D260= 2613353715115) at /usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/ip_frag_intern= al.c:286 #2 0x00007ffff7c00280 in rte_ipv4_frag_reassemble_packet (tbl=3D0x7fff7a32= ce80, dr=3D0x7fff7a32c900, mb=3D0x7fff8b71b480, tms=3D,=20 ip_hdr=3D) at /usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/rte_ipv4_reass= embly.c:160 (gdb) f 0 #0 ip_frag_lookup (tbl=3Dtbl@entry=3D0x7fff7a32ce80, key=3Dkey@entry=3D0x7= ffff6eeee10, tms=3Dtms@entry=3D2602613353715115, free=3Dfree@entry=3D0x7ffff6eeedb8,=20 stale=3Dstale@entry=3D0x7ffff6eeedc0) at /usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/ip_frag_intern= al.c:379 379 if (ip_frag_key_cmp(key, &p1[i].key) =3D=3D 0) (gdb) f 1 #1 0x00007ffff7c021f6 in ip_frag_find (tbl=3Dtbl@entry=3D0x7fff7a32ce80, dr=3Ddr@entry=3D0x7fff7a32c900, key=3Dkey@entry=3D0x7ffff6eeee10, tms=3D260= 2613353715115) at /usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/ip_frag_intern= al.c:286 286 if ((pkt =3D ip_frag_lookup(tbl, key, tms, &free, &stale)) =3D=3D N= ULL) { (gdb) f 2 #2 0x00007ffff7c00280 in rte_ipv4_frag_reassemble_packet (tbl=3D0x7fff7a32= ce80, dr=3D0x7fff7a32c900, mb=3D0x7fff8b71b480, tms=3D,=20 ip_hdr=3D) at /usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/rte_ipv4_reass= embly.c:160 160 if ((fp =3D ip_frag_find(tbl, dr, &key, tms)) =3D=3D NULL) { Is this a known issue? Are there any workaround? --=20 You are receiving this mail because: You are the assignee for the bug.=