From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 265] i40e flow flush & add new flow will occur segfault
Date: Mon, 06 May 2019 07:41:29 +0000 [thread overview]
Message-ID: <bug-265-3@http.bugs.dpdk.org/> (raw)
Message-ID: <20190506074129.9h_50wvn64qI-0mgqdiZdJa7dLAZTvAyg51NNsynKas@z> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=265
Bug ID: 265
Summary: i40e flow flush & add new flow will occur segfault
Product: DPDK
Version: 18.11
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: kangzy1982@qq.com
Target Milestone: ---
in this commit id 2e67a7fbf3ffd64cf18a565535135794b62af74d
* net/i40e: config flow director automatically
function i40e_flow_destroy/i40e_flow_flush_fdir_filter add a i40e_fdir_teardown
call! it will release all fdir resource!
when call flow flush and add a new flow（i40e_flow_add_del_fdir_filter ->
i40e_flow_fdir_filter_programming） will access a null pointer!
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-05-06 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 7:41 bugzilla [this message]
2019-05-06 7:41 ` bugzilla
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-265-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 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).