From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Mordechay Haimovsky <motih@mellanox.com>
Cc: John Daley <johndale@cisco.com>, "dev@dpdk.org" <dev@dpdk.org>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: fix flow list command
Date: Wed, 10 Oct 2018 18:35:43 +0200 [thread overview]
Message-ID: <20181010163542.GO18937@6wind.com> (raw)
In-Reply-To: <AM0PR05MB44359C11D163109EF2BC79B8D2E00@AM0PR05MB4435.eurprd05.prod.outlook.com>
On Wed, Oct 10, 2018 at 04:27:59PM +0000, Mordechay Haimovsky wrote:
> Hi Adrien,
> You are correct, the bug is not where we thought it is, moreover the fix breaks
> the CLI and should be rejected.
> We investigated more and found that the bug is in the port_flow_query routine
> Which passes an incorrect argument to rte_flow_conv as follows:
> ret = rte_flow_conv(RTE_FLOW_CONV_OP_ACTION_NAME_PTR,
> &name, sizeof(name), action, &error);
> While it should pass onlt the action type as follows:
> ret = rte_flow_conv(RTE_FLOW_CONV_OP_ACTION_NAME_PTR,
> &name, sizeof(name),
> (void *)(uintptr_t)action->type, &error);
> As done in port_flow_list routine (which works)
> if (rte_flow_conv(RTE_FLOW_CONV_OP_ACTION_NAME_PTR,
> &name, sizeof(name),
> (void *)(uintptr_t)action->type,
> NULL) <= 0)
> And according to the parameters description of rte_flow_conv_name (called by rte_flow_conv):
> * @param[in] src
> * Depending on @p is_action, source pattern item or action type cast as a
> * pointer.
>
> Modifying port_flow_query accordingly solves the issue.
> I will issue a new patch tonight.
Indeed, I confirm this is the right bug to address (and seems like I did not
validate rte_flow_query() properly.) Thanks for taking care of it!
--
Adrien Mazarguil
6WIND
prev parent reply other threads:[~2018-10-10 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 22:51 John Daley
2018-10-10 8:37 ` Adrien Mazarguil
2018-10-10 16:27 ` Mordechay Haimovsky
2018-10-10 16:35 ` Adrien Mazarguil [this message]
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=20181010163542.GO18937@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=johndale@cisco.com \
--cc=motih@mellanox.com \
/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).