From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: chengongming1900@outlook.com, robot@bytheb.org
Subject: |FAILURE| pw142184 [PATCH v3] vhost: fix crash caused by accessing a freed vsocket
Date: Sun, 7 Jul 2024 23:23:36 -0400 [thread overview]
Message-ID: <20240708032336.332828-1-robot@bytheb.org> (raw)
In-Reply-To: <TYAP286MB064974AD63043F26745F5A83D8DA2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/142184/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9832707113
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-clang-stdatomic" failed at step Build and test
"ubuntu-22.04-clang-asan+doc+tests" failed at step Build and test
"fedora:39-clang" failed at step Build
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
}
^
../lib/vhost/vhost_thread.c:10:2: note: mutex acquired here
rte_rwlock_read_lock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:16:2: error: releasing mutex 'vhost_thread_lock' that was not held [-Werror,-Wthread-safety-analysis]
rte_rwlock_read_unlock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:23:1: error: mutex 'vhost_thread_lock' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
../lib/vhost/vhost_thread.c:22:2: note: mutex acquired here
rte_rwlock_write_lock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:28:2: error: releasing mutex 'vhost_thread_lock' that was not held [-Werror,-Wthread-safety-analysis]
rte_rwlock_write_unlock(&vhost_thread_lock);
^
4 errors generated.
[423/2988] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost.c.o'.
[424/2988] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_user.c.o'.
[425/2988] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_crypto.c.o'.
[426/2988] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_virtio_net.c.o'.
[427/2988] Compiling C object 'lib/76b5a35@@rte_pipeline@sta/pipeline_rte_table_action.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
}
^
../lib/vhost/vhost_thread.c:10:2: note: mutex acquired here
rte_rwlock_read_lock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:16:2: error: releasing mutex 'vhost_thread_lock' that was not held [-Werror,-Wthread-safety-analysis]
rte_rwlock_read_unlock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:23:1: error: mutex 'vhost_thread_lock' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
../lib/vhost/vhost_thread.c:22:2: note: mutex acquired here
rte_rwlock_write_lock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:28:2: error: releasing mutex 'vhost_thread_lock' that was not held [-Werror,-Wthread-safety-analysis]
rte_rwlock_write_unlock(&vhost_thread_lock);
^
4 errors generated.
[438/4073] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_user.c.o'.
[439/4073] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost.c.o'.
[440/4073] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_crypto.c.o'.
[441/4073] Compiling C object 'lib/76b5a35@@rte_pipeline@sta/pipeline_rte_table_action.c.o'.
[442/4073] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_virtio_net.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
####################################################################################
#### [Begin job log] "fedora:39-clang" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:39-clang" at step Build
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2024-07-08 3:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TYAP286MB064974AD63043F26745F5A83D8DA2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
2024-07-08 2:03 ` |SUCCESS| " qemudev
2024-07-08 2:07 ` qemudev
2024-07-08 2:25 ` checkpatch
2024-07-08 3:23 ` 0-day Robot [this message]
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=20240708032336.332828-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=chengongming1900@outlook.com \
--cc=test-report@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).