automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	Gongming Chen <chengongming1900@outlook.com>
Subject: |FAILURE| pw142183 [PATCH] [v2] vhost: fix crash caused by accessing
Date: Sun, 07 Jul 2024 20:43:47 -0700 (PDT)	[thread overview]
Message-ID: <668b6073.d40a0220.136b1.f7dbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <TYAP286MB0649F57394FD92719A1F99D8D8DA2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/142183

_Testing issues_

Submitter: Gongming Chen <chengongming1900@outlook.com>
Date: Monday, July 08 2024 02:17:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9cbdb606e5d04de04be3d9f70f0e76551e8c9a36

142183 --> testing issues

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 39           | PEND           |
+---------------------+----------------+
| Fedora 39 (Clang)   | FAIL           |
+---------------------+----------------+
| Fedora 38 (Clang)   | PEND           |
+---------------------+----------------+
| Fedora 40           | PEND           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PEND           |
+---------------------+----------------+
| RHEL9               | PEND           |
+---------------------+----------------+
| RHEL8               | PEND           |
+---------------------+----------------+
| openSUSE Leap 15    | PEND           |
+---------------------+----------------+
| Ubuntu 20.04        | PEND           |
+---------------------+----------------+
| Ubuntu 24.04        | PEND           |
+---------------------+----------------+
| Ubuntu 22.04        | PEND           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+

==== 20 line log output for Fedora 39 (Clang) (dpdk_unit_test): ====
../lib/vhost/vhost_thread.c:10:2: note: mutex acquired here
10 |         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]
16 |         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]
23 | }
| ^
../lib/vhost/vhost_thread.c:22:2: note: mutex acquired here
22 |         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]
28 |         rte_rwlock_write_unlock(&vhost_thread_lock);
|         ^
4 errors generated.
[410/2905] Generating mldev.sym_chk with a meson_exe.py custom command.
[411/2905] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost.c.o'.
[412/2905] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_vhost_crypto.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30445/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-07-08  3:43 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <TYAP286MB0649F57394FD92719A1F99D8D8DA2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
2024-07-08  1:51 ` |SUCCESS| pw142183 [PATCH v2] vhost: fix crash caused by accessing a freed vsocket qemudev
2024-07-08  1:56 ` qemudev
2024-07-08  2:18 ` |WARNING| " checkpatch
2024-07-08  2:45 ` |SUCCESS| pw142183 [PATCH] [v2] vhost: fix crash caused by accessing dpdklab
2024-07-08  2:47 ` dpdklab
2024-07-08  2:48 ` dpdklab
2024-07-08  2:49 ` dpdklab
2024-07-08  2:52 ` dpdklab
2024-07-08  2:54 ` dpdklab
2024-07-08  2:55 ` dpdklab
2024-07-08  2:55 ` |PENDING| " dpdklab
2024-07-08  2:55 ` dpdklab
2024-07-08  2:56 ` dpdklab
2024-07-08  2:56 ` |SUCCESS| " dpdklab
2024-07-08  2:58 ` |PENDING| " dpdklab
2024-07-08  2:59 ` dpdklab
2024-07-08  3:00 ` dpdklab
2024-07-08  3:03 ` |FAILURE| pw142183 [PATCH v2] vhost: fix crash caused by accessing a freed vsocket 0-day Robot
2024-07-08  3:03 ` |PENDING| pw142183 [PATCH] [v2] vhost: fix crash caused by accessing dpdklab
2024-07-08  3:05 ` |SUCCESS| " dpdklab
2024-07-08  3:07 ` |PENDING| " dpdklab
2024-07-08  3:08 ` dpdklab
2024-07-08  3:09 ` dpdklab
2024-07-08  3:09 ` dpdklab
2024-07-08  3:10 ` dpdklab
2024-07-08  3:10 ` dpdklab
2024-07-08  3:13 ` dpdklab
2024-07-08  3:13 ` |SUCCESS| " dpdklab
2024-07-08  3:13 ` |PENDING| " dpdklab
2024-07-08  3:14 ` dpdklab
2024-07-08  3:14 ` dpdklab
2024-07-08  3:15 ` dpdklab
2024-07-08  3:16 ` dpdklab
2024-07-08  3:18 ` |FAILURE| " dpdklab
2024-07-08  3:19 ` dpdklab
2024-07-08  3:19 ` |PENDING| " dpdklab
2024-07-08  3:19 ` dpdklab
2024-07-08  3:19 ` |FAILURE| " dpdklab
2024-07-08  3:19 ` |PENDING| " dpdklab
2024-07-08  3:20 ` dpdklab
2024-07-08  3:21 ` dpdklab
2024-07-08  3:21 ` dpdklab
2024-07-08  3:24 ` |SUCCESS| " dpdklab
2024-07-08  3:26 ` |FAILURE| " dpdklab
2024-07-08  3:26 ` |PENDING| " dpdklab
2024-07-08  3:27 ` |FAILURE| " dpdklab
2024-07-08  3:29 ` dpdklab
2024-07-08  3:30 ` |SUCCESS| " dpdklab
2024-07-08  3:30 ` |FAILURE| " dpdklab
2024-07-08  3:31 ` |PENDING| " dpdklab
2024-07-08  3:34 ` dpdklab
2024-07-08  3:36 ` dpdklab
2024-07-08  3:38 ` dpdklab
2024-07-08  3:39 ` |FAILURE| " dpdklab
2024-07-08  3:41 ` |PENDING| " dpdklab
2024-07-08  3:41 ` |FAILURE| " dpdklab
2024-07-08  3:41 ` |PENDING| " dpdklab
2024-07-08  3:42 ` |FAILURE| " dpdklab
2024-07-08  3:43 ` dpdklab
2024-07-08  3:43 ` dpdklab [this message]
2024-07-08  3:44 ` dpdklab
2024-07-08  3:44 ` dpdklab
2024-07-08  3:44 ` |SUCCESS| " dpdklab
2024-07-08  3:45 ` |FAILURE| " dpdklab
2024-07-08  3:46 ` dpdklab
2024-07-08  3:47 ` dpdklab
2024-07-08  3:47 ` dpdklab
2024-07-08  3:48 ` dpdklab
2024-07-08  3:48 ` dpdklab
2024-07-08  3:50 ` dpdklab
2024-07-08  3:51 ` dpdklab
2024-07-08  3:51 ` dpdklab
2024-07-08  3:52 ` dpdklab
2024-07-08  3:53 ` dpdklab
2024-07-08  3:53 ` dpdklab
2024-07-08  3:55 ` dpdklab
2024-07-08  3:57 ` dpdklab
2024-07-08  3:57 ` dpdklab
2024-07-08  3:57 ` dpdklab
2024-07-08  3:57 ` dpdklab
2024-07-08  3:58 ` dpdklab
2024-07-08  4:01 ` |SUCCESS| " dpdklab
2024-07-08  4:27 ` |FAILURE| " dpdklab
2024-07-09 11:02 ` |SUCCESS| " dpdklab
2024-07-09 11:15 ` dpdklab
2024-07-14  0:04 ` dpdklab
2024-07-14 11:03 ` dpdklab
2024-07-14 17:34 ` dpdklab
2024-07-15 10:27 ` dpdklab
2024-07-15 10:31 ` dpdklab

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=668b6073.d40a0220.136b1.f7dbSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=chengongming1900@outlook.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).