From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 628] Possible deadlock in testpmd
Date: Thu, 28 Jan 2021 16:21:24 +0000 [thread overview]
Message-ID: <bug-628-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=628
Bug ID: 628
Summary: Possible deadlock in testpmd
Product: DPDK
Version: 20.08
Hardware: x86
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: High
Component: testpmd
Assignee: dev@dpdk.org
Reporter: maxime.coquelin@redhat.com
CC: thomas@monjalon.net, xianghao3@jd.com
Depends on: 611
Target Milestone: ---
+++ This bug was initially created as a clone of Bug #611 +++
Recently we see a deadlock in vdpa example app if SIGTERM signal is sent at
early start stage.After debuging, we suspect it's due to vhost_user.mutex is
requested twice,once by start sequence start_vdpa(), the other by SIGTERM
signal handler which calling close_vdpa().
Also checked other example apps, seems they all have same issue.
+++
Testpmd seems also impacted. Indeed, pmd_test_exit() gets called, which turns
out to call dev_stop() and dev_close() ethdev ops that almost all take spinlock
or mutexes.
Referenced Bugs:
https://bugs.dpdk.org/show_bug.cgi?id=611
[Bug 611] deadlock in example vdpa app
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-01-28 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-628-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.