From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: David Marchand <david.marchand@redhat.com>,
Mike Pattrick <mkp@redhat.com>
Cc: "Xing, Beilei" <beilei.xing@intel.com>,
"murphyx.yang@intel.com" <murphyx.yang@intel.com>,
dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>
Subject: RE: [PATCH] net/i40e: Populate error in flow_parse_fdir_pattern
Date: Thu, 24 Mar 2022 09:15:55 +0000 [thread overview]
Message-ID: <0ef0da67b8074e1faee8052526b081d6@intel.com> (raw)
In-Reply-To: <CAJFAV8zn5SfFEHK6FcLWpN5vLsvhCgOJ5gE1Sb1V4AYbuEBiTw@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Tuesday, March 22, 2022 4:36 PM
> To: Mike Pattrick <mkp@redhat.com>
> Cc: Xing, Beilei <beilei.xing@intel.com>; murphyx.yang@intel.com; dev
> <dev@dpdk.org>; dpdk stable <stable@dpdk.org>
> Subject: Re: [PATCH] net/i40e: Populate error in flow_parse_fdir_pattern
>
Renamed title to
"net/i40e: populate error in FDIR flow pattern parser"
To fix check-git-log warning
> Hello Mike,
>
> On Tue, Mar 22, 2022 at 4:20 AM Mike Pattrick <mkp@redhat.com> wrote:
> >
> > Errors from i40e_flow_parse_fdir_pattern() can bubble up to
> > rte_flow_create. If rte_flow_error is not initialized a caller may
> > dereference error->message. This may be uninitialized memory, leading
> > to a segemntation fault.
> >
> > Signed-off-by: Mike Pattrick <mkp@redhat.com>
> > Fixes: 4a072ad43442 ("net/i40e: fix flow director config after flow
> > validate")
> > Cc: stable@dpdk.org
>
> Nit: the convention in DPDK is to have a block with the Fixes: and Cc:
> lines together first, then the rest of the tags in a second block.
>
> Fixes: 4a072ad43442 ("net/i40e: fix flow director config after flow validate")
> Cc: stable@dpdk.org
> <empty line>
> Signed-off-by: Mike Pattrick <mkp@redhat.com>
>
>
> > ---
> > drivers/net/i40e/i40e_flow.c | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/net/i40e/i40e_flow.c
> > b/drivers/net/i40e/i40e_flow.c index e0cf996200..4f3808cb5f 100644
> > --- a/drivers/net/i40e/i40e_flow.c
> > +++ b/drivers/net/i40e/i40e_flow.c
> > @@ -3142,8 +3142,11 @@ i40e_flow_parse_fdir_pattern(struct
> rte_eth_dev *dev,
> > /* Check if the input set is valid */
> > if (i40e_validate_input_set(pctype, RTE_ETH_FILTER_FDIR,
> > input_set) != 0) {
> > - PMD_DRV_LOG(ERR, "Invalid input set");
> > - return -EINVAL;
> > + rte_flow_error_set(error, EINVAL,
> > + RTE_FLOW_ERROR_TYPE_ITEM,
> > + item,
> > + "Invalid input set");
> > + return -rte_errno;
> > }
> >
> > filter->input.flow_ext.input_set = input_set;
> > --
> > 2.27.0
> >
>
> Reviewed-by: David Marchand <david.marchand@redhat.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
>
>
> --
> David Marchand
prev parent reply other threads:[~2022-03-24 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 3:19 Mike Pattrick
2022-03-22 8:35 ` David Marchand
2022-03-24 9:15 ` Zhang, Qi Z [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=0ef0da67b8074e1faee8052526b081d6@intel.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=mkp@redhat.com \
--cc=murphyx.yang@intel.com \
--cc=stable@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).