From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: chengongming1900@outlook.com, robot@bytheb.org
Subject: |FAILURE| pw139067 [PATCH] vhost: fix crash caused by accessing a freed vsocket
Date: Wed, 3 Apr 2024 00:25:51 -0400 [thread overview]
Message-ID: <20240403042551.2736656-1-robot@bytheb.org> (raw)
In-Reply-To: <TYAP286MB0649A160A9852720E0F3D67BD83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/139067/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8532931313
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:14:2: note: mutex acquired here
rte_rwlock_read_lock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:20: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:27:1: error: mutex 'vhost_thread_lock' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
../lib/vhost/vhost_thread.c:26:2: note: mutex acquired here
rte_rwlock_write_lock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:32: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.
[424/2955] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost.c.o'.
[425/2955] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_user.c.o'.
[426/2955] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_crypto.c.o'.
[427/2955] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_virtio_net.c.o'.
[428/2955] 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:14:2: note: mutex acquired here
rte_rwlock_read_lock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:20: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:27:1: error: mutex 'vhost_thread_lock' is still held at the end of function [-Werror,-Wthread-safety-analysis]
}
^
../lib/vhost/vhost_thread.c:26:2: note: mutex acquired here
rte_rwlock_write_lock(&vhost_thread_lock);
^
../lib/vhost/vhost_thread.c:32: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/4036] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_user.c.o'.
[439/4036] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost.c.o'.
[440/4036] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_crypto.c.o'.
[441/4036] Compiling C object 'lib/76b5a35@@rte_pipeline@sta/pipeline_rte_table_action.c.o'.
[442/4036] 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-----------------------------
next prev parent reply other threads:[~2024-04-03 4:25 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TYAP286MB0649A160A9852720E0F3D67BD83D2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
2024-04-03 3:03 ` |SUCCESS| " qemudev
2024-04-03 3:27 ` checkpatch
2024-04-03 4:25 ` 0-day Robot [this message]
2024-04-03 8:22 ` |SUCCESS| pw139067 [PATCH] vhost: fix crash caused by accessing a fr dpdklab
2024-04-03 8:24 ` dpdklab
2024-04-03 8:27 ` dpdklab
2024-04-03 8:33 ` dpdklab
2024-04-03 8:33 ` dpdklab
2024-04-03 8:39 ` dpdklab
2024-04-03 8:53 ` dpdklab
2024-04-03 8:53 ` dpdklab
2024-04-03 8:54 ` dpdklab
2024-04-03 8:55 ` dpdklab
2024-04-03 8:55 ` dpdklab
2024-04-03 8:56 ` dpdklab
2024-04-03 8:56 ` dpdklab
2024-04-03 8:56 ` dpdklab
2024-04-03 8:57 ` dpdklab
2024-04-03 8:57 ` dpdklab
2024-04-03 8:57 ` dpdklab
2024-04-03 8:58 ` dpdklab
2024-04-03 8:58 ` dpdklab
2024-04-03 8:59 ` dpdklab
2024-04-03 9:15 ` |FAILURE| " dpdklab
2024-04-03 9:16 ` dpdklab
2024-04-03 9:17 ` dpdklab
2024-04-03 9:18 ` dpdklab
2024-04-03 9:19 ` dpdklab
2024-04-03 9:19 ` dpdklab
2024-04-03 9:20 ` |SUCCESS| " dpdklab
2024-04-03 9:22 ` |FAILURE| " dpdklab
2024-04-03 9:23 ` dpdklab
2024-04-03 9:23 ` dpdklab
2024-04-03 9:24 ` dpdklab
2024-04-03 9:24 ` dpdklab
2024-04-03 9:24 ` dpdklab
2024-04-03 9:25 ` dpdklab
2024-04-03 9:25 ` dpdklab
2024-04-03 9:25 ` dpdklab
2024-04-03 9:26 ` dpdklab
2024-04-03 9:26 ` dpdklab
2024-04-03 9:26 ` dpdklab
2024-04-03 9:27 ` dpdklab
2024-04-03 9:27 ` dpdklab
2024-04-03 9:27 ` dpdklab
2024-04-03 9:27 ` dpdklab
2024-04-03 9:28 ` dpdklab
2024-04-03 9:28 ` dpdklab
2024-04-03 9:28 ` dpdklab
2024-04-03 9:28 ` dpdklab
2024-04-03 9:28 ` dpdklab
2024-04-03 9:28 ` |SUCCESS| " dpdklab
2024-04-03 9:29 ` |FAILURE| " dpdklab
2024-04-03 9:29 ` dpdklab
2024-04-03 9:29 ` dpdklab
2024-04-03 9:30 ` dpdklab
2024-04-03 9:30 ` |SUCCESS| " dpdklab
2024-04-03 9:30 ` |FAILURE| " dpdklab
2024-04-03 9:31 ` dpdklab
2024-04-03 9:31 ` dpdklab
2024-04-03 9:32 ` dpdklab
2024-04-03 9:32 ` dpdklab
2024-04-03 9:32 ` dpdklab
2024-04-03 9:33 ` dpdklab
2024-04-03 9:34 ` dpdklab
2024-04-03 9:35 ` dpdklab
2024-04-03 9:36 ` |SUCCESS| " dpdklab
2024-04-03 9:37 ` dpdklab
2024-04-03 9:37 ` |FAILURE| " dpdklab
2024-04-03 9:38 ` dpdklab
2024-04-03 9:39 ` dpdklab
2024-04-03 9:40 ` dpdklab
2024-04-03 9:40 ` dpdklab
2024-04-03 9:42 ` dpdklab
2024-04-03 9:44 ` dpdklab
2024-04-03 9:44 ` dpdklab
2024-04-03 9:45 ` dpdklab
2024-04-03 9:46 ` dpdklab
2024-04-03 9:52 ` dpdklab
2024-04-03 9:52 ` dpdklab
2024-04-03 10:11 ` dpdklab
2024-04-03 11:01 ` dpdklab
2024-04-03 11:03 ` dpdklab
2024-04-03 11:18 ` |SUCCESS| " dpdklab
2024-04-03 13:08 ` |FAILURE| " dpdklab
2024-04-03 13:35 ` |SUCCESS| " dpdklab
2024-04-03 13:55 ` dpdklab
2024-04-04 4:00 ` dpdklab
2024-04-04 4:30 ` dpdklab
2024-04-04 5:13 ` dpdklab
2024-04-04 5:56 ` dpdklab
2024-04-04 6:01 ` dpdklab
2024-04-07 1:11 ` |SUCCESS| pw139067 [PATCH] vhost: fix crash caused by accessing a freed vsocket qemudev
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=20240403042551.2736656-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).