DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: zhao wei <wei.zhao1@gmail.com>
Subject: Re: [dpdk-dev] [PATCH v1] net/ixgbe: add more check in n-tuple filter
Date: Fri, 3 Feb 2017 01:21:46 +0000	[thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA0203FC25@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <0909b05d-2058-b51a-f974-f2d686392a5d@intel.com>

Hi,  Ferruh

> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Monday, January 23, 2017 8:23 PM
> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> Cc: zhao wei <wei.zhao1@gmail.com>
> Subject: Re: [dpdk-dev] [PATCH v1] net/ixgbe: add more check in n-tuple
> filter
> 
> On 1/23/2017 3:32 AM, Wei Zhao wrote:
> > Add more check on the mask of src_addr, dst_addr and next_proto_id in
> > n-tuple filter rule pattern parser.If do not add such check, it maybe
> > cause error in pattern parser.
> >
> > Signed-off-by: zhao wei <wei.zhao1@gmail.com>
> > ---
> >  drivers/net/ixgbe/ixgbe_flow.c | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/ixgbe/ixgbe_flow.c
> > b/drivers/net/ixgbe/ixgbe_flow.c index 82aceed..8f78eee 100644
> > --- a/drivers/net/ixgbe/ixgbe_flow.c
> > +++ b/drivers/net/ixgbe/ixgbe_flow.c
> > @@ -331,7 +331,10 @@ cons_parse_ntuple_filter(const struct
> rte_flow_attr *attr,
> >  	    ipv4_mask->hdr.packet_id ||
> >  	    ipv4_mask->hdr.fragment_offset ||
> >  	    ipv4_mask->hdr.time_to_live ||
> > -	    ipv4_mask->hdr.hdr_checksum) {
> > +	    ipv4_mask->hdr.hdr_checksum ||
> > +	    !ipv4_mask->hdr.next_proto_id ||
> > +	    !ipv4_mask->hdr.dst_addr ||
> > +	    !ipv4_mask->hdr.src_addr ||) {
> 
> The '||' at the end seems extra.
> 
> Also can you please confirm your sign off?
> 
> >  			rte_flow_error_set(error,
> >  			EINVAL, RTE_FLOW_ERROR_TYPE_ITEM,
> >  			item, "Not supported by ntuple filter");
> >

This patch has been change to suspended on patchwork net.
Thank you.

      reply	other threads:[~2017-02-03  1:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23  3:32 Wei Zhao
2017-01-23 12:22 ` Ferruh Yigit
2017-02-03  1:21   ` Zhao1, Wei [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=A2573D2ACFCADC41BB3BE09C6DE313CA0203FC25@PGSMSX103.gar.corp.intel.com \
    --to=wei.zhao1@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=wei.zhao1@gmail.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).