From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B257F48A46; Wed, 29 Oct 2025 14:52:42 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4B4F1402A6; Wed, 29 Oct 2025 14:52:42 +0100 (CET) Received: from mail-pj1-f54.google.com (mail-pj1-f54.google.com [209.85.216.54]) by mails.dpdk.org (Postfix) with ESMTP id F12404028C for ; Mon, 27 Oct 2025 17:59:12 +0100 (CET) Received: by mail-pj1-f54.google.com with SMTP id 98e67ed59e1d1-339d7c403b6so4903982a91.2 for ; Mon, 27 Oct 2025 09:59:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1761584352; x=1762189152; darn=dpdk.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Cu+3t/eyT8ZIfY9IFqomNhmzJgRnnNblNo8MmxxL8kA=; b=JDV9IWtn0pCSKaya28ZVs4JP3uS9J41yRgQK6HfoNyvkJusF3zmV7vlf2XVLal8sFs 9chzvJUpVnapSa5/mdEpAuhrzx7dGCVMfCWwk3R0cpqOnnUDe1X0zBj5I1+LyIb4lxgo sKacVSwHjzYtqapqH3G5TIOmsA5HWbM5RO6EuFUvaZ7Tu2dSXPDtv9f+KYjxXtHRU0LJ x+MCXhgf47xlvwWOpics9eh8siFmSsmAbn3bxOyeLoeSp+OQCRU3R5hxDJB0TSpKoy5E 2zAWWm8pQsuWqn9oemL/Nbbn6iFUvtkHK5v2F6D9K3zj9UYdsB8JT6SfHoyIg7WbatTa 812g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761584352; x=1762189152; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Cu+3t/eyT8ZIfY9IFqomNhmzJgRnnNblNo8MmxxL8kA=; b=rwgx4053dABvnX+jz5TqKxTNfwq626cU6qpSI+5ceib72373naevk1uFaweDXoyBmu uWOVYC1qw+AYzfo/dZUVOLg2pGhVYxlNTALUuGO6il/n70fq/rryG6F8RVke280LcF5h 2lUM+R8pefb/on6LvrMO1XPOr0cmn5z5Cb14hVrAsu9T2IDVSVETThwe7nDelEREwQwN 8dkMl/xdZk4Nu48Jrf3V1xsai8LWPGfn2fjkQTCs9d+c0ioibJRh4VmZjw4uy9eegtUc FlLGYT4PW+rPbF0eMMBqQ6hdgDmAZwpVc7yKc5StzJxyWZSoMWVZm2tw2PDkvpN61kqL 0Pzg== X-Gm-Message-State: AOJu0Yy7ugYed2MO7H1SW5qRJLn3MRiOgiNrbP2tAbz0OPFJf0M9xk+g S1H5uV1SNn+sCguxohSUTT+nM8OGRGXx+PaFvLWsX3GqUHMVVBFwVeyunOZwFsSFjiaBfl2pi7V ex/rvYLFT2KSrPrSAeQbthfpBEANXl8IXoBQqLt+q X-Gm-Gg: ASbGncvmRGyad2YCq8x6RbY3q9V6iwWjiaw4ulaA8QEgXKUQuFwPGVSol3XURDZ3aX/ 6PflOmtEsjI69BE2ouBFOAkTlrANfaGeDf1/yVXrbJJqroKsLDACNgWWYkU42CKVmBsm0uKvcgG ztFX9Wz+IJRY0qdD9Srrk+SIBqK3n8e803MT1+JP7qly+MgE7YLIywYEUTpGa4n3ocbbjawBF+N q9t4gK4HmFGJ6C9NAclYqPFYYzgg81IO+6wDDo1dQi7kg5fSKkUBafw1Wss3lrzf+SxJw== X-Google-Smtp-Source: AGHT+IHOQzBhdXPTY6wwhsD8voN3QYyRkP77X8hZDSufDomrbpcPjc9B2mKQTQrkpkLiPm2jbcCly4tgKQXeL57Jrec= X-Received: by 2002:a17:90b:514f:b0:33e:30cb:216e with SMTP id 98e67ed59e1d1-340279e5393mr523088a91.5.1761584351795; Mon, 27 Oct 2025 09:59:11 -0700 (PDT) MIME-Version: 1.0 From: Shoaib Choudhary Date: Mon, 27 Oct 2025 22:29:00 +0530 X-Gm-Features: AWmQ_bk-NNqJtJtS-BqOX5RfowRd0FVsKzsapSkBvlaldNPsgOAxIHlIS-FHWRI Message-ID: Subject: Segmentation Fault in IPsec_MB PMD When Resetting Crypto Device Stats After Upgrade to DPDK 24.11.3 To: dev@dpdk.org Content-Type: multipart/alternative; boundary="00000000000087e258064226d1c3" X-Mailman-Approved-At: Wed, 29 Oct 2025 14:52:41 +0100 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --00000000000087e258064226d1c3 Content-Type: text/plain; charset="UTF-8" *Description:* After upgrading from DPDK 24.11 to 24.11.3, we are encountering a segmentation fault in the IPsec_MB PMD (librte_crypto_ipsec_mb.so.25) when attempting to reset crypto device statistics using rte_cryptodev_stats_reset(). This issue was not observed in DPDK 24.11. *Reproduction Context:* The crash occurs during automated traffic tests that exercise GTP loopback scenarios on a DPDK-based system. The test suite covers both fragmented and non-fragmented packets, and uses multiple crypto algorithms (AES, SNOW3G, ZUC) with Out-of-Place (OOP) processing enabled and disabled. Traffic is sent through the datapath, and statistics are collected and reset as part of the test flow. The segmentation fault is consistently triggered when resetting crypto device stats after such traffic tests. *Crash Details:* - Faulting function: rte_cryptodev_stats_reset() (called from application code) - Faulting library: librte_crypto_ipsec_mb.so.25 - Fault address: 0x58 - Only occurs in DPDK 24.11.3; not seen in 24.11 *Workarounds Attempted:* - Added device validation and error handling before stats reset - Implemented workaround to avoid direct stats reset (using baseline stats), Crash persists despite these changes - After implementing logic to skip rte_cryptodev_stats_reset() for IPsec_MB, SNOW3G, and AESNI_MB PMDs, the original segmentation fault was avoided. However, we then observed a separate crash during subsequent crypto device operations (such as session creation or device configuration). *Request:* Is this a known regression in DPDK 24.11.3? Are there any recommended fixes or patches available? Any guidance on further debugging or mitigation would be appreciated. Regards, Shoaib --00000000000087e258064226d1c3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Descriptio= n:
After upgrading f= rom DPDK 24.11 to 24.11.3, we are encountering a segmentation fault in the = IPsec_MB PMD (librte_crypto_ipsec_mb.so.25) when attempting to reset crypto= device statistics using=C2=A0rte_cryptodev_stats_reset(). This issue was n= ot observed in DPDK 24.11.

Reproduction Context:
The crash occurs during automated traffi= c tests that exercise GTP loopback scenarios on a DPDK-based system. The te= st suite covers both fragmented and non-fragmented packets, and uses multip= le crypto algorithms (AES, SNOW3G, ZUC) with Out-of-Place (OOP) processing = enabled and disabled. Traffic is sent through the datapath, and statistics = are collected and reset as part of the test flow. The segmentation fault is= consistently triggered when resetting crypto device stats after such traff= ic tests.

Crash Details:

  • Faulting function:=C2=A0rte_cryptodev_stats_reset()=C2=A0(called from appl= ication code)
  • Fault address: 0x58
    • <= li class=3D"gmail-x_MsoNormal" style=3D"margin:0in;font-size:12pt;font-fami= ly:Aptos">Only occurs in DPDK 24.1= 1.3; not seen in 24.11

Workarounds Attempted:

  • Added device validation and error handling b= efore stats reset
  • Implemented workaround to avoid direct stats reset (using baseline st= ats),=C2=A0Crash persists d= espite these changes
  • After implementing logic to skip=C2=A0rte_cryptodev_stats_reset()= =C2=A0for IPsec_MB, SNOW3G, and AESNI_MB PMDs, the original segmentation fa= ult was avoided. However, we then observed a separate crash during subseque= nt crypto device operations (such as session creation or device configurati= on).

Request:
= Is this a known regression in DPDK 24.11.3? Are there any recommended fixes= or patches available? Any guidance on further debugging or mitigation woul= d be appreciated.


Regards,

Shoaib


--00000000000087e258064226d1c3--