DPDK patches and discussions
 help / color / Atom feed
* [dpdk-dev] [Bug 338] IP Reassembly with more 4 packets Segfault
@ 2019-08-13  3:05 bugzilla
  0 siblings, 0 replies; only message in thread
From: bugzilla @ 2019-08-13  3:05 UTC (permalink / raw)
  To: dev

https://bugs.dpdk.org/show_bug.cgi?id=338

            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 <DPDK IP addr> -s
6000

(gdb) bt
#0  ip_frag_lookup (tbl=tbl@entry=0x7fff7a32ce80, key=key@entry=0x7ffff6eeee10,
tms=tms@entry=2602613353715115, free=free@entry=0x7ffff6eeedb8, 
    stale=stale@entry=0x7ffff6eeedc0) at
/usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/ip_frag_internal.c:379
#1  0x00007ffff7c021f6 in ip_frag_find (tbl=tbl@entry=0x7fff7a32ce80,
dr=dr@entry=0x7fff7a32c900, key=key@entry=0x7ffff6eeee10, tms=2602613353715115)
    at
/usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/ip_frag_internal.c:286
#2  0x00007ffff7c00280 in rte_ipv4_frag_reassemble_packet (tbl=0x7fff7a32ce80,
dr=0x7fff7a32c900, mb=0x7fff8b71b480, tms=<optimized out>, 
    ip_hdr=<optimized out>) at
/usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/rte_ipv4_reassembly.c:160

(gdb) f 0
#0  ip_frag_lookup (tbl=tbl@entry=0x7fff7a32ce80, key=key@entry=0x7ffff6eeee10,
tms=tms@entry=2602613353715115, free=free@entry=0x7ffff6eeedb8, 
    stale=stale@entry=0x7ffff6eeedc0) at
/usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/ip_frag_internal.c:379
379     if (ip_frag_key_cmp(key, &p1[i].key) == 0)

(gdb) f 1
#1  0x00007ffff7c021f6 in ip_frag_find (tbl=tbl@entry=0x7fff7a32ce80,
dr=dr@entry=0x7fff7a32c900, key=key@entry=0x7ffff6eeee10, tms=2602613353715115)
    at
/usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/ip_frag_internal.c:286
286     if ((pkt = ip_frag_lookup(tbl, key, tms, &free, &stale)) == NULL) {

(gdb) f 2
#2  0x00007ffff7c00280 in rte_ipv4_frag_reassemble_packet (tbl=0x7fff7a32ce80,
dr=0x7fff7a32c900, mb=0x7fff8b71b480, tms=<optimized out>, 
    ip_hdr=<optimized out>) at
/usr/src/debug/dpdk-17.11.2-6.fc30.x86_64/lib/librte_ip_frag/rte_ipv4_reassembly.c:160
160     if ((fp = ip_frag_find(tbl, dr, &key, tms)) == NULL) {

Is this a known issue? Are there any workaround?

-- 
You are receiving this mail because:
You are the assignee for the bug.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-13  3:05 [dpdk-dev] [Bug 338] IP Reassembly with more 4 packets Segfault bugzilla

DPDK patches and discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/ public-inbox