Bug ID 1294
Summary recieve sig 11 when call rte_ip_frag_table_create on primary forked process
Product DPDK
Version 21.11
Hardware All
OS All
Status UNCONFIRMED
Severity normal
Priority Normal
Component core
Assignee dev@dpdk.org
Reporter 779198444@qq.com
Target Milestone ---

hi,my team is going do our own business in primary forked process, to make sure
business won't affect the primary, we may refork the business process many
times,
now there comes the problem:
when the first time fork the process ,it runs good, but, it recieved sig-11 on
call rte_ip_frag_table_create  after the second time fork. here is the
backtrace:
(gdb) bt
#0  0x00007fb913af4dc5 in malloc_elem_insert () from /lib/libdpdk.so
#1  0x00007fb913af5e97 in alloc_pages_on_heap () from /lib/libdpdk.so
#2  0x00007fb913af6154 in try_expand_heap () from /lib/libdpdk.so
#3  0x00007fb913af65a1 in alloc_more_mem_on_socket () from /lib/libdpdk.so
#4  0x00007fb913af6c9a in malloc_heap_alloc () from /lib/libdpdk.so
#5  0x00007fb913af84e3 in rte_malloc_socket () from /lib/libdpdk.so
#6  0x00007fb913af863f in rte_zmalloc_socket () from /lib/libdpdk.so
#7  0x00007fb913a4343f in rte_ip_frag_table_create () from /lib/libdpdk.so

does the primary do not allow malloc and free memery at forking process?
could you do me a favor? thanks
          


You are receiving this mail because: