From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1294] recieve sig 11 when call rte_ip_frag_table_create on primary forked process
Date: Mon, 25 Sep 2023 12:23:01 +0000 [thread overview]
Message-ID: <bug-1294-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1631 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1294
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:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3513 bytes --]
next reply other threads:[~2023-09-25 12:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 12:23 bugzilla [this message]
2023-09-25 15:13 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1294-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).