From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126182 [PATCH] ring: fix use after free in ring release
Date: Tue, 18 Apr 2023 01:38:41 +0000 (UTC) [thread overview]
Message-ID: <20230418013841.B4DF86008C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126182
_Testing PASS_
Submitter: Yunjian Wang <wangyunjian@huawei.com>
Date: Monday, April 17 2023 13:11:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126182 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26016/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-18 1:38 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 1:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 0:32 dpdklab
2023-04-18 0:00 dpdklab
2023-04-17 23:35 dpdklab
2023-04-17 23:34 dpdklab
2023-04-17 23:20 dpdklab
2023-04-17 22:53 dpdklab
2023-04-17 18:54 dpdklab
2023-04-17 18:47 dpdklab
2023-04-17 18:45 dpdklab
2023-04-17 18:42 dpdklab
2023-04-17 18:42 dpdklab
2023-04-17 18:39 dpdklab
2023-04-17 18:31 dpdklab
2023-04-17 18:29 dpdklab
2023-04-17 18:28 dpdklab
2023-04-17 18:19 dpdklab
2023-04-17 18:16 dpdklab
2023-04-17 18:09 dpdklab
2023-04-17 18:07 dpdklab
2023-04-17 17:49 dpdklab
2023-04-17 17:45 dpdklab
2023-04-17 17:43 dpdklab
2023-04-17 17:31 dpdklab
2023-04-17 17:30 dpdklab
2023-04-17 17:30 dpdklab
2023-04-17 17:18 dpdklab
2023-04-17 17:15 dpdklab
2023-04-17 17:15 dpdklab
2023-04-17 17:14 dpdklab
2023-04-17 17:14 dpdklab
2023-04-17 17:09 dpdklab
2023-04-17 17:04 dpdklab
2023-04-17 17:01 dpdklab
2023-04-17 16:56 dpdklab
2023-04-17 16:52 dpdklab
2023-04-17 16:51 dpdklab
2023-04-17 16:47 dpdklab
2023-04-17 16:47 dpdklab
2023-04-17 16:45 dpdklab
2023-04-17 16:44 dpdklab
2023-04-17 16:44 dpdklab
2023-04-17 16:40 dpdklab
2023-04-17 16:40 dpdklab
2023-04-17 16:38 dpdklab
2023-04-17 16:09 dpdklab
2023-04-17 16:06 dpdklab
2023-04-17 16:00 dpdklab
2023-04-17 15:57 dpdklab
2023-04-17 15:56 dpdklab
2023-04-17 15:56 dpdklab
2023-04-17 15:53 dpdklab
2023-04-17 15:51 dpdklab
2023-04-17 15:50 dpdklab
2023-04-17 15:49 dpdklab
2023-04-17 15:45 dpdklab
2023-04-17 15:43 dpdklab
2023-04-17 15:41 dpdklab
[not found] <d175f9250542291dd0b86f4587a5fde018b945b1.1681736644.git.wangyunjian@huawei.com>
2023-04-17 13:02 ` qemudev
2023-04-17 13:06 ` qemudev
2023-04-17 13:12 ` checkpatch
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=20230418013841.B4DF86008C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).