From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: stable@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>,
Chenbo Xia <chenbo.xia@intel.com>,
Yuanhan Liu <yliu@fridaylinux.org>
Subject: [PATCH] vhost: avoid sleeping under mutex
Date: Wed, 22 Mar 2023 18:05:24 +0100 [thread overview]
Message-ID: <20230322170524.2314715-1-david.marchand@redhat.com> (raw)
Covscan reported:
2. dpdk-21.11/lib/vhost/socket.c:852: lock_acquire: Calling function
"pthread_mutex_lock" acquires lock "vhost_user.mutex".
23. dpdk-21.11/lib/vhost/socket.c:955: sleep: Call to
"vhost_user_reconnect_init" might sleep while holding lock
"vhost_user.mutex".
# 953| vsocket->reconnect =
!(flags & RTE_VHOST_USER_NO_RECONNECT);
# 954| if (vsocket->reconnect && reconn_tid == 0) {
# 955|-> if (vhost_user_reconnect_init() != 0)
# 956| goto out_mutex;
# 957| }
The reason for this warning is that vhost_user_reconnect_init() creates a
ctrl thread and calls nanosleep waiting for this thread to be ready,
while vhost_user.mutex is taken.
Move the call to vhost_user_reconnect_init() out of this mutex.
While at it, a pthread_t value should be considered opaque.
Instead of relying reconn_tid == 0, use an internal flag in
vhost_user_reconnect_init().
Coverity issue: 373686
Bugzilla ID: 981
Fixes: e623e0c6d8a5 ("vhost: add reconnect ability")
Cc: stable@dpdk.org
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
lib/vhost/socket.c | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/lib/vhost/socket.c b/lib/vhost/socket.c
index 669c322e12..21002848e6 100644
--- a/lib/vhost/socket.c
+++ b/lib/vhost/socket.c
@@ -498,8 +498,12 @@ vhost_user_client_reconnect(void *arg __rte_unused)
static int
vhost_user_reconnect_init(void)
{
+ static bool reconn_init_done;
int ret;
+ if (reconn_init_done)
+ return 0;
+
ret = pthread_mutex_init(&reconn_list.mutex, NULL);
if (ret < 0) {
VHOST_LOG_CONFIG("thread", ERR, "%s: failed to initialize mutex\n", __func__);
@@ -515,6 +519,8 @@ vhost_user_reconnect_init(void)
VHOST_LOG_CONFIG("thread", ERR,
"%s: failed to destroy reconnect mutex\n",
__func__);
+ } else {
+ reconn_init_done = true;
}
return ret;
@@ -866,6 +872,11 @@ rte_vhost_driver_register(const char *path, uint64_t flags)
if (!path)
return -1;
+ if ((flags & RTE_VHOST_USER_CLIENT) != 0 &&
+ (flags & RTE_VHOST_USER_NO_RECONNECT) == 0 &&
+ vhost_user_reconnect_init() != 0)
+ return -1;
+
pthread_mutex_lock(&vhost_user.mutex);
if (vhost_user.vsocket_cnt == MAX_VHOST_SOCKET) {
@@ -961,11 +972,7 @@ rte_vhost_driver_register(const char *path, uint64_t flags)
}
if ((flags & RTE_VHOST_USER_CLIENT) != 0) {
- vsocket->reconnect = !(flags & RTE_VHOST_USER_NO_RECONNECT);
- if (vsocket->reconnect && reconn_tid == 0) {
- if (vhost_user_reconnect_init() != 0)
- goto out_mutex;
- }
+ vsocket->reconnect = (flags & RTE_VHOST_USER_NO_RECONNECT) == 0;
} else {
vsocket->is_server = true;
}
--
2.39.2
next reply other threads:[~2023-03-22 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 17:05 David Marchand [this message]
2023-05-11 8:10 ` Xia, Chenbo
2023-05-15 11:22 ` David Marchand
2023-05-15 11:18 ` [PATCH v2] " David Marchand
2023-05-15 15:51 ` 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=20230322170524.2314715-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=stable@dpdk.org \
--cc=yliu@fridaylinux.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).