From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126079 [PATCH] crypto/qat: fix stack buffer overflow in SGL loop
Date: Fri, 14 Apr 2023 22:30:33 +0000 (UTC) [thread overview]
Message-ID: <20230414223033.CB23B6008C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126079
_Testing PASS_
Submitter: Power, Ciara <ciara.power@intel.com>
Date: Friday, April 14 2023 12:31:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126079 --> testing pass
Test environment and result as below:
+----------------------+---------------------------+------------------------------+--------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest |
+======================+===========================+==============================+==============+
| Debian 11 | PASS | PASS | SKIPPED |
+----------------------+---------------------------+------------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | PASS |
+----------------------+---------------------------+------------------------------+--------------+
Debian 11
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25999/
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-14 22:30 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 22:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 16:48 dpdklab
2023-04-15 10:46 dpdklab
2023-04-15 10:45 dpdklab
2023-04-15 10:12 dpdklab
2023-04-15 10:11 dpdklab
2023-04-15 7:32 dpdklab
2023-04-15 7:00 dpdklab
2023-04-15 6:12 dpdklab
2023-04-15 6:07 dpdklab
2023-04-15 6:03 dpdklab
2023-04-15 5:47 dpdklab
2023-04-15 5:42 dpdklab
2023-04-15 5:30 dpdklab
2023-04-15 4:06 dpdklab
2023-04-15 0:15 dpdklab
2023-04-15 0:14 dpdklab
2023-04-15 0:01 dpdklab
2023-04-15 0:00 dpdklab
2023-04-14 23:55 dpdklab
2023-04-14 23:52 dpdklab
2023-04-14 23:52 dpdklab
2023-04-14 23:51 dpdklab
2023-04-14 23:39 dpdklab
2023-04-14 23:33 dpdklab
2023-04-14 23:22 dpdklab
2023-04-14 23:19 dpdklab
2023-04-14 23:17 dpdklab
2023-04-14 23:15 dpdklab
2023-04-14 23:15 dpdklab
2023-04-14 23:13 dpdklab
2023-04-14 23:11 dpdklab
2023-04-14 22:55 dpdklab
2023-04-14 22:45 dpdklab
2023-04-14 22:44 dpdklab
2023-04-14 22:40 dpdklab
2023-04-14 22:33 dpdklab
2023-04-14 22:32 dpdklab
2023-04-14 22:28 dpdklab
2023-04-14 22:26 dpdklab
2023-04-14 22:25 dpdklab
2023-04-14 22:24 dpdklab
2023-04-14 22:20 dpdklab
2023-04-14 22:17 dpdklab
2023-04-14 21:24 dpdklab
2023-04-14 21:16 dpdklab
2023-04-14 21:00 dpdklab
2023-04-14 20:48 dpdklab
2023-04-14 20:47 dpdklab
2023-04-14 20:47 dpdklab
2023-04-14 20:46 dpdklab
2023-04-14 20:39 dpdklab
[not found] <20230414123131.575412-1-ciara.power@intel.com>
2023-04-14 12:33 ` checkpatch
2023-04-14 12:44 ` qemudev
2023-04-14 12:48 ` qemudev
2023-04-14 13:39 ` 0-day Robot
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=20230414223033.CB23B6008C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--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).