All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 941] [dpdk-22.03] core dump when create fdir rule with bad arguments
Date: Tue, 01 Mar 2022 06:28:03 +0000	[thread overview]
Message-ID: <bug-941-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=941

            Bug ID: 941
           Summary: [dpdk-22.03] core dump when create fdir rule with bad
                    arguments
           Product: DPDK
           Version: unspecified
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: testpmd
          Assignee: dev@dpdk.org
          Reporter: zhiminx.huang@intel.com
  Target Milestone: ---

ENV:
dpdk-22.03-rc2:305769000c40a4fdf1ed0cf24c157b447b91ea7d
OS: redhat8.5/4.18.0-348.el8.x86_64
Compiler: gcc version 8.5.0 20210514 (Red Hat 8.5.0-4)
Hardware platform: Intel(R) Xeon(R) Gold 6139 CPU @ 2.30GHz
NIC hardware: Intel Corporation Ethernet Controller E810-C for QSFP [8086:1592]
NIC firmware: 
ice: 1.8.2_2_gca97f0c8_dirty
firmware-version: 3.20 0x8000d0ec 1.3141.0
pkg: ICE OS Default Package version 1.3.28.0

Reproduced Steps:
1.
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:ca:00.0 0000:ca:00.1
0000:ca:00.2 0000:ca:00.3

2.
x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0x3e -n 4 -a
0000:ca:00.0,pipeline-mode-support=1 --log-level="ice,7" -- -i --portmask=0x1
--rxq=10 --txq=10

3.
flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is
192.168.0.3 tos is 4 / tcp src is 25 dst is 23 / end

output:
Segmentation fault (core dumped)

expect output:
Bad arguments

dpdk bad commit id:
04cc665fab38e2a382f6886e57c97b78e92cea46 is the first bad commit
commit 04cc665fab38e2a382f6886e57c97b78e92cea46
Author: Alexander Kozyrev <akozyrev@nvidia.com>
Date:   Wed Feb 23 05:02:35 2022 +0200

    app/testpmd: add flow template management

    Add testpmd support for the rte_flow_pattern_template and
    rte_flow_actions_template APIs. Provide the command line interface
    for the template creation/destruction. Usage example:
      testpmd> flow pattern_template 0 create pattern_template_id 2
               template eth dst is 00:16:3e:31:15:c3 / end
      testpmd> flow actions_template 0 create actions_template_id 4
               template drop / end mask drop / end
      testpmd> flow actions_template 0 destroy actions_template 4
      testpmd> flow pattern_template 0 destroy pattern_template 2

    Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
    Acked-by: Ori Kam <orika@nvidia.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2022-03-01  6:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-941-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.