From: David Marchand <david.marchand@redhat.com>
To: Feifei Wang <feifei.wang2@arm.com>
Cc: dev <dev@dpdk.org>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH 0/3] ring clean up
Date: Wed, 8 Jul 2020 16:51:00 +0200 [thread overview]
Message-ID: <CAJFAV8w2wbzLh_4zqHr4kg49w3qQpcnbW06tshFmMfiVvkwBMA@mail.gmail.com> (raw)
In-Reply-To: <20200703102651.8918-1-feifei.wang2@arm.com>
On Fri, Jul 3, 2020 at 12:27 PM Feifei Wang <feifei.wang2@arm.com> wrote:
>
> Do some work for ring refactoring, which includes:
> 1. remove experimental tags
> 2. use element APIs to implement legacy APIs
This series triggers unit test failures.
https://travis-ci.com/github/ovsrobot/dpdk/builds/174196115
https://travis-ci.com/github/ovsrobot/dpdk/jobs/357314387#L1092
In my env:
test_refcnt_slave started at lcore 22
test_refcnt_slave started at lcore 23
test_refcnt_slave started at lcore 24
test_refcnt_slave started at lcore 25
test_refcnt_slave started at lcore 26
test_refcnt_slave started at lcore 27
test_refcnt_master started at lcore 1
Thread 6 "lcore-slave-4" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff4723400 (LWP 374679)]
0x00000000007e29d0 in rte_pktmbuf_free (m=0xffff000100010000) at
../../dpdk/lib/librte_mbuf/rte_mbuf.h:1407
1407 m_next = m->next;
Missing separate debuginfos, use: dnf debuginfo-install
dbus-libs-1.12.18-1.fc31.x86_64 elfutils-libelf-0.179-2.fc31.x86_64
jansson-2.12-4.fc31.x86_64 libbpf-0.0.7-1.fc31.x86_64
libbsd-0.9.1-4.fc31.x86_64 libfdt-1.6.0-1.fc31.x86_64
libgcc-9.3.1-2.fc31.x86_64 libgcrypt-1.8.5-1.fc31.x86_64
libnl3-3.5.0-1.fc31.x86_64 libpcap-1.9.1-2.fc31.x86_64
lz4-libs-1.9.1-1.fc31.x86_64 numactl-libs-2.0.12-3.fc31.x86_64
openssl-libs-1.1.1g-1.fc31.x86_64 systemd-libs-243.8-1.fc31.x86_64
xz-libs-5.2.5-1.fc31.x86_64 zlib-1.2.11-20.fc31.x86_64
(gdb) bt
#0 0x00000000007e29d0 in rte_pktmbuf_free (m=0xffff000100010000) at
../../dpdk/lib/librte_mbuf/rte_mbuf.h:1407
#1 test_refcnt_slave (arg=0x17f7e3940) at ../../dpdk/app/test/test_mbuf.c:1016
#2 0x0000000000446a89 in eal_thread_loop (arg=<optimized out>) at
../../dpdk/lib/librte_eal/linux/eal_thread.c:127
#3 0x00007ffff709c4e2 in start_thread () from /usr/lib64/libpthread.so.0
#4 0x00007ffff6fc96a3 in clone () from /usr/lib64/libc.so.6
Thanks.
--
David Marchand
next prev parent reply other threads:[~2020-07-08 14:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 10:26 Feifei Wang
2020-07-03 10:26 ` [dpdk-dev] [PATCH 1/3] ring: remove experimental tag for ring reset API Feifei Wang
2020-07-03 16:16 ` Kinsella, Ray
2020-07-03 18:46 ` Honnappa Nagarahalli
2020-07-06 6:23 ` Kinsella, Ray
2020-07-07 3:19 ` Feifei Wang
2020-07-07 7:40 ` Kinsella, Ray
2020-07-03 10:26 ` [dpdk-dev] [PATCH 2/3] ring: remove experimental tag for ring element APIs Feifei Wang
2020-07-03 16:17 ` Kinsella, Ray
2020-07-07 14:44 ` Ananyev, Konstantin
2020-07-03 10:26 ` [dpdk-dev] [PATCH 3/3] ring: use element APIs to implement legacy APIs Feifei Wang
2020-07-07 5:19 ` Feifei Wang
2020-07-07 14:04 ` Ananyev, Konstantin
2020-07-07 16:21 ` Honnappa Nagarahalli
2020-07-08 3:19 ` Feifei Wang
2020-07-07 20:07 ` David Christensen
2020-07-08 1:30 ` Feifei Wang
2020-07-08 1:21 ` Feifei Wang
2020-07-07 14:45 ` Ananyev, Konstantin
2020-07-08 14:51 ` David Marchand [this message]
2020-07-08 17:05 ` [dpdk-dev] [PATCH 0/3] ring clean up Ananyev, Konstantin
2020-07-08 20:33 ` Honnappa Nagarahalli
2020-07-09 2:27 ` Feifei Wang
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=CAJFAV8w2wbzLh_4zqHr4kg49w3qQpcnbW06tshFmMfiVvkwBMA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=feifei.wang2@arm.com \
--cc=nd@arm.com \
/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).