From: Kevin Traynor <ktraynor@redhat.com>
To: "Xu, HailinX" <hailinx.xu@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
Luca Boccassi <bluca@debian.org>,
Thomas Monjalon <thomas@monjalon.net>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
Shani Peretz <shperetz@nvidia.com>
Subject: Re: 24.11.4 patches review and test
Date: Fri, 19 Dec 2025 10:22:13 +0000 [thread overview]
Message-ID: <0e65bc7c-1281-4258-a9d3-d055fd4b50fd@redhat.com> (raw)
In-Reply-To: <SJ5PPF04AA7285F22060F7A805954B3CB049FA9A@SJ5PPF04AA7285F.namprd11.prod.outlook.com>
On 19/12/2025 02:33, Xu, HailinX wrote:
>>> 1. virtio_ipsec_cryptodev_func/test_virtio_aes_cbc_sha1_hmac:vhost-user meet Segmentation fault after sending package
> After dual confirmation, this is an invalid error and cannot be reproduce
>
>>> 2. Bug 1849 - [dpdk-22.11.11rc1] virtio_perf_cryptodev_func/test_virtio_aes_cbc_sha1_hmac: dpdk-test-crypto-perf EAL: Error: Invalid memory
> It has been fixed on the 24.11 LTS latest version.
>
Hi Hailin. ok, thank you for the testing and reports!
>
> Regards,
> Xu, Hailin
>
>> -----Original Message-----
>> From: Kevin Traynor <ktraynor@redhat.com>
>> Sent: Thursday, December 18, 2025 1:16 AM
>> To: Xu, HailinX <hailinx.xu@intel.com>; stable@dpdk.org
>> Cc: Mcnamara, John <john.mcnamara@intel.com>; Luca Boccassi
>> <bluca@debian.org>; Thomas Monjalon <thomas@monjalon.net>;
>> Richardson, Bruce <bruce.richardson@intel.com>; Gowrishankar
>> Muthukrishnan <gmuthukrishn@marvell.com>; Burakov, Anatoly
>> <anatoly.burakov@intel.com>; Shani Peretz <shperetz@nvidia.com>
>> Subject: Re: 24.11.4 patches review and test
>>
>> On 17/12/2025 08:39, Xu, HailinX wrote:
>>>> -----Original Message-----
>>>> From: Kevin Traynor <ktraynor@redhat.com>
>>>> Sent: Friday, December 5, 2025 5:59 PM
>>>> To: stable@dpdk.org
>>>> Cc: dev@dpdk.org; Abhishek Marathe
>> <Abhishek.Marathe@microsoft.com>;
>>>> Ali Alnubani <alialnu@nvidia.com>; David Christensen
>>>> <drc@linux.vnet.ibm.com>; Hemant Agrawal <hemant.agrawal@nxp.com>;
>>>> Jerin Jacob <jerinj@marvell.com>; Mcnamara, John
>>>> <john.mcnamara@intel.com>; Ju-Hyoung Lee <juhlee@microsoft.com>;
>>>> Kevin Traynor <ktraynor@redhat.com>; Luca Boccassi
>>>> <bluca@debian.org>; Pei Zhang <pezhang@redhat.com>; Raslan
>> Darawsheh
>>>> <rasland@nvidia.com>; Thomas Monjalon <thomas@monjalon.net>;
>>>> yanghliu@redhat.com
>>>> Subject: 24.11.4 patches review and test
>>>>
>>>> Hi all,
>>>>
>>>> Here is a list of patches targeted for stable release 24.11.4.
>>>>
>>>> The planned date for the final release is 18th December.
>>>>
>>>> Please help with testing and validation of your use cases and report
>>>> any issues/results with reply-all to this mail. For the final release
>>>> the fixes and reported validations will be added to the release notes.
>>>>
>>>> A release candidate tarball can be found at:
>>>>
>>>> https://dpdk.org/browse/dpdk-stable/tag/?id=v24.11.4-rc1
>>>>
>>>> These patches are located at branch 24.11 of dpdk-stable repo:
>>>> https://dpdk.org/browse/dpdk-stable/
>>>>
>>>> Thanks.
>>>>
>>>> Kevin
>>>>
>>>> ---
>>> Update the test status for Intel part. dpdk24.11.4-rc1 all validation test
>> done. found two new issues.
>>>
>>
>> Hi Hailin. Thanks for testing and reporting these.
>>
>>> New issues:
>>> 1. virtio_ipsec_cryptodev_func/test_virtio_aes_cbc_sha1_hmac:
>>> vhost-user meet Segmentation fault after sending package
>>
>> Were you able to dissect which commit is causing this ?
>>
>> Is it the same commit as below ?
>>
>> That was the only change to drivers/crypto/virtio/*
>>
>>> 2. Bug 1849 - [dpdk-22.11.11rc1]
>>> virtio_perf_cryptodev_func/test_virtio_aes_cbc_sha1_hmac:
>>> dpdk-test-crypto-perf EAL: Error: Invalid memory
>>
>> As you've dissected this, similar to 22.11 I've reverted below commit.
>>
>> Can you re-run these 2 tests with the offending patch reverted ?
>>
>> commit 2effa20c58fba0b2702681c7ee063786abc36f4c
>> Author: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
>> Date: Sat Oct 11 10:07:03 2025 +0530
>>
>> crypto/virtio: fix cookies leak
>>
>> [ upstream commit 8b0d855fd98c6c88665489fdba12f8e603deae21 ]
>>
>>>
>>> known issue:
>>> 1. Linkville vfs can't forward packets -. has two fix patch not merge into
>> 24.11 LTS
>>> - has fix patches:
>>> https://patches.dpdk.org/project/dpdk/list/?series=34939&archive=both&
>>> state=*
>>>
>>
>> on those patches
>> - 2/3 is applied on 24.11 branch.
>> - 1/3 and 3/3 are not tagged for backport.
>> 1/3 is just a clean up and not really needed.
>> 3/3 is a bit intrusive and does not apply. It is too close to the
>> 24.11.4 release now, but we could consider a custom backport for 24.11.5 if
>> it's really needed.
>>
>> thanks,
>> Kevin.
>>
>>> * Build & CFLAG compile: cover the build test with latest GCC/Clang version
>> on the following OS(all passed)
>>> - Ubuntu25.04/Ubuntu24.04.3
>>> - RHEL9.6/RHEL10
>>> - Fedora42
>>> - FreeBSD14.3
>>> - SUSE15.6
>>> - OpenAnolis8.10
>>> - OpenEuler24.04-SP2
>>> - AzureLinux3.0
>>>
>>> * Function tests: All test done and there are one known issue and found two
>> new issues.
>>> - i40E-(XXV710, X722) PF/VF: test scenarios including
>> basic/RTE_FLOW/TSO/Jumboframe/checksum
>> offload/mac_filter/VLAN/VXLAN/RSS, etc.
>>> - IXGBE-(82599, E610) PF/VF: test scenarios including
>> basic/RTE_FLOW/TSO/Jumboframe/checksum
>> offload/mac_filter/VLAN/VXLAN/RSS, etc.
>>> - ICE-(E810, E2100) PF/VF: test scenarios including basic/Switch/Package
>> Management/Flow Director/Advanced Tx/Advanced RSS/ACL/DCF/Flexible
>> Descriptor, etc.
>>> - IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test -
>> QAT&SW/FIB library, etc.
>>> - Virtio: both function and performance test are covered. Such as
>> PVP/Virtio_loopback/virtio-user loopback/virtio-net VM2VM perf
>> testing/VMAWARE ESXI 8.0, etc.
>>> - Cryptodev: test scenarios including Cryptodev API testing/CompressDev
>> ISA-L/QAT/ZLIB PMD Testing/FIPS, etc.
>>> - DLB: test scenarios including DLB2.0 and DLB2.5
>>> - Other: test scenarios including AF_XDP, Power, CBDMA, DSA
>>>
>>> * Performance test: All test done and passed
>>> - Thoughput Performance
>>> - Cryptodev Latency
>>> - PF/VF NIC single core
>>> - XXV710/E810 NIC Performance
>
next prev parent reply other threads:[~2025-12-19 10:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 9:59 Kevin Traynor
2025-12-09 9:23 ` Yanghang Liu
2025-12-10 17:03 ` Kevin Traynor
2025-12-17 8:39 ` Xu, HailinX
2025-12-17 17:15 ` Kevin Traynor
2025-12-18 1:40 ` Xu, HailinX
2025-12-19 2:33 ` Xu, HailinX
2025-12-19 10:22 ` Kevin Traynor [this message]
2025-12-18 18:38 ` Ali Alnubani
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=0e65bc7c-1281-4258-a9d3-d055fd4b50fd@redhat.com \
--to=ktraynor@redhat.com \
--cc=anatoly.burakov@intel.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=gmuthukrishn@marvell.com \
--cc=hailinx.xu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=shperetz@nvidia.com \
--cc=stable@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).