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 C6073456BC; Fri, 26 Jul 2024 12:38:32 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 549CF40DFD; Fri, 26 Jul 2024 12:38:32 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id B588C4064F for ; Fri, 26 Jul 2024 12:32:42 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id A5A67456BD; Fri, 26 Jul 2024 12:32:42 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [DPDK/examples Bug 1502] [dpdk-24.07] l3fwdacl/l3fwdacl_acl_rule: core dump when receiving packets Date: Fri, 26 Jul 2024 10:32:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: examples X-Bugzilla-Version: 24.07 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: songx.jiale@intel.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17219899620.d37d.3360234 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 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 --17219899620.d37d.3360234 Date: Fri, 26 Jul 2024 12:32:42 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1502 Bug ID: 1502 Summary: [dpdk-24.07] l3fwdacl/l3fwdacl_acl_rule: core dump when receiving packets Product: DPDK Version: 24.07 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: Normal Component: examples Assignee: dev@dpdk.org Reporter: songx.jiale@intel.com Target Milestone: --- [Environment] DPDK version:=20 dpdk24.07-rc3=EF=BC=9A82c47f005b9a0a1e3a649664b7713443d18abe43 Other software versions: N/A. OS: Anolis OS 8.8/5.10.134-13.an8.x86_64 Compiler: gcc version 8.5.0 20210514 Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz NIC hardware: Intel Corporation Ethernet Controller E810-C for SFP [8086:15= 93] (rev 01) NIC driver: ice-1.14.11 NIC firmware: 4.50 0x8001d8b6 1.3597.0 [Test Setup] 1.compile dpdk rm -rf x86_64-native-linuxapp-gcc CC=3Dgcc meson -Denable_kmods=3DTrue -Dlibdir=3Dlib --default-library=3Dsta= tic -Db_sanitize=3Daddress -Dexamples=3Dl3fwd x86_64-native-linuxapp-gcc ninja -C x86_64-native-linuxapp-gcc=20=20 2. bind pf to vfio-pci=20 ./usertools/dpdk-devbind.py -b vfio-pci 18:00.0 18:00.1 3.prepare acl rules=20 echo '' > /root/rule_ipv4.db echo 'R0.0.0.0/0 0.0.0.0/0 0 : 65535 0 : 65535 0x00/0x00 1' >> /root/rule_ipv4.db echo '' > /root/rule_ipv6.db echo 'R0:0:0:0:0:0:0:0/0 0:0:0:0:0:0:0:0/0 0 : 65535 0 : 65535 0x00/0x00 1'= >> /root/rule_ipv6.db echo '' > /root/rule_ipv4.db echo @200.10.0.1/32 0.0.0.0/0 0 : 65535 0 : 65535 0x00/0x00 >> /root/rule_ipv4.db echo R0.0.0.0/0 0.0.0.0/0 0 : 65535 0 : 65535 0x00/0x00 1 >> /root/rule_ipv= 4.db 4.launch dpdk-l3fwd=20 x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd -l 1-4 -n 4 -a 0000:18:00.0 = -a 0000:18:00.1 --force-max-simd-bitwidth=3D0 -- -p 0x3 --lookup acl --config=3D"(0,0,2),(1,0,3)" --rule_ipv4=3D"/root/rule_ipv4.db" --rule_ipv6=3D"/root/rule_ipv6.db" --parse-ptype=20=20 5.Send packets sendp([Ether(dst=3D"{rx_port_mac}")/IP(src=3D"200.10.0.1",dst=3D"100.10.0.1= ")/UDP(sport=3D11,dport=3D101)],iface=3D"ens7",count=3D1,inter=3D0,verbose= =3DFalse) [Show the output from the previous commands.] Segmentation fault [Expected Result] The application can receive and send packages normally. [Regression] Is this issue a regression: (Y/N)Y commit aa7c6077c19bd39b48ac17cd844b91f0dd03319f Author: Konstantin Ananyev Date: Thu May 2 16:28:16 2024 +0100 examples/l3fwd: avoid packets reorder in ACL mode In ACL mode l3fwd first do classify() and send() for ipv4 packets, then the same procedure for ipv6. That might cause packets reordering within one ingress queue. Probably not a big deal, as order within each flow are still preserved, but better to be avoided anyway. Specially considering that in other modes (lpm, fib, em) l3fwd does preserve the order no matter of packet's IP version. This patch aims to make ACL mode to behave in the same manner and preserve packet's order within the same ingress queue. Also these changes allow ACL mode to use common (and hopefully better optimized) send_packets_multi() function at Tx pa= th. Signed-off-by: Konstantin Ananyev examples/l3fwd/l3fwd_acl.c | 125 ++++++++++++++++++++++++----------= ---- examples/l3fwd/l3fwd_acl_scalar.h | 71 ++++++++++++---------- 2 files changed, 118 insertions, 78 deletions --=20 You are receiving this mail because: You are the assignee for the bug.= --17219899620.d37d.3360234 Date: Fri, 26 Jul 2024 12:32:42 +0200 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1502
Summary [dpdk-24.07] l3fwdacl/l3fwdacl_acl_rule: core dump when recei= ving packets
Product DPDK
Version 24.07
Hardware x86
OS Linux
Status UNCONFIRMED
Severity normal
Priority Normal
Component examples
Assignee dev@dpdk.org
Reporter songx.jiale@intel.com
Target Milestone --- 

[Environment]
DPDK version:=20
dpdk24.07-rc3=EF=BC=9A82c47f005b9a0a1e3a649664b7713443d18abe43
Other software versions: N/A.
OS: Anolis OS 8.8/5.10.134-13.an8.x86_64
Compiler: gcc version 8.5.0 20210514
Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz
NIC hardware: Intel Corporation Ethernet Controller E810-C for SFP [8086:15=
93]
(rev 01)
NIC driver: ice-1.14.11
NIC firmware: 4.50 0x8001d8b6 1.3597.0

[Test Setup]
1.compile dpdk
rm -rf x86_64-native-linuxapp-gcc
CC=3Dgcc meson -Denable_kmods=3DTrue -Dlibdir=3Dlib --default-library=3Dsta=
tic
-Db_sanitize=3Daddress -Dexamples=3Dl3fwd x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc=20=20
2. bind pf to vfio-pci=20
./usertools/dpdk-devbind.py -b vfio-pci 18:00.0 18:00.1

3.prepare acl rules=20
echo '' > /root/rule_ipv4.db
echo 'R0.0.0.0/0 0.0.0.0/0 0 : 65535 0 : 65535 0x00/0x00 1' >>
/root/rule_ipv4.db
echo '' > /root/rule_ipv6.db
echo 'R0:0:0:0:0:0:0:0/0 0:0:0:0:0:0:0:0/0 0 : 65535 0 : 65535 0x00/0x00 1'=
 >>
/root/rule_ipv6.db
echo '' > /root/rule_ipv4.db
echo @200.10.0.1/32 0.0.0.0/0 0 : 65535 0 : 65535 0x00/0x00  >>
/root/rule_ipv4.db
echo R0.0.0.0/0 0.0.0.0/0 0 : 65535 0 : 65535 0x00/0x00 1 >> /root/ru=
le_ipv4.db

4.launch dpdk-l3fwd=20
x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd -l 1-4 -n 4 -a 0000:18:00.0 =
-a
0000:18:00.1 --force-max-simd-bitwidth=3D0 -- -p 0x3 --lookup acl
--config=3D"(0,0,2),(1,0,3)" --rule_ipv4=3D"/root/rule_ipv4.=
db"
--rule_ipv6=3D"/root/rule_ipv6.db" --parse-ptype=20=20
5.Send packets
sendp([Ether(dst=3D"{rx_port_mac}")/IP(src=3D"200.10.0.1&quo=
t;,dst=3D"100.10.0.1")/UDP(sport=3D11,dport=3D101)],iface=3D"=
;ens7",count=3D1,inter=3D0,verbose=3DFalse)

[Show the output from the previous commands.]

Segmentation fault

[Expected Result]

The application can receive and send packages normally.

[Regression]
Is this issue a regression: (Y/N)Y

commit aa7c6077c19bd39b48ac17cd844b91f0dd03319f
Author: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Date:   Thu May 2 16:28:16 2024 +0100

    examples/l3fwd: avoid packets reorder in ACL mode

    In ACL mode l3fwd first do classify() and send() for ipv4 packets,
    then the same procedure for ipv6.
    That might cause packets reordering within one ingress queue.
    Probably not a big deal, as order within each flow are still preserved,
    but better to be avoided anyway.
    Specially considering that in other modes (lpm, fib, em)
    l3fwd does preserve the order no matter of packet's IP version.
    This patch aims to make ACL mode to behave in the same manner
    and preserve packet's order within the same ingress queue.
    Also these changes allow ACL mode to use common
    (and hopefully better optimized) send_packets_multi() function at Tx pa=
th.

    Signed-off-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>

 examples/l3fwd/l3fwd_acl.c        | 125 ++++++++++++++++++++++++----------=
----
 examples/l3fwd/l3fwd_acl_scalar.h |  71 ++++++++++++----------
 2 files changed, 118 insertions, 78 deletions

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17219899620.d37d.3360234--