DPDK patches and discussions
 help / color / Atom feed
From: "P, Venkata Suresh Kumar" <venkata.suresh.kumar.p@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] pipeline: fix jump instruction parsing
Date: Fri, 16 Oct 2020 14:17:54 +0000
Message-ID: <BYAPR11MB3077C34ECAC2E4FC1FBA16B699030@BYAPR11MB3077.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20201016135757.76761-1-cristian.dumitrescu@intel.com>

Thanks a lot Cristian for sending the patches for review.

Thanks & Regards,
Suresh.

-----Original Message-----
From: Dumitrescu, Cristian <cristian.dumitrescu@intel.com> 
Sent: Friday, October 16, 2020 7:28 PM
To: dev@dpdk.org
Cc: P, Venkata Suresh Kumar <venkata.suresh.kumar.p@intel.com>; Khangar, Churchill <churchill.khangar@intel.com>; Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
Subject: [PATCH 2/2] pipeline: fix jump instruction parsing

From: Churchill Khangar <churchill.khangar@intel.com>

This patch fixes the jump if not valid header instruction parsing

Fixes: b3947e25bed4 ("pipeline: introduce SWX jump and return instructions")
Cc: cristian.dumitrescu@intel.com

Signed-off-by: Churchill Khangar <churchill.khangar@intel.com>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
---
 lib/librte_pipeline/rte_swx_pipeline.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/librte_pipeline/rte_swx_pipeline.c b/lib/librte_pipeline/rte_swx_pipeline.c
index 2c9fbf4..9d64611 100644
--- a/lib/librte_pipeline/rte_swx_pipeline.c
+++ b/lib/librte_pipeline/rte_swx_pipeline.c
@@ -4658,7 +4658,7 @@ struct_field_parse(struct rte_swx_pipeline *p,  {
 	struct header *h;
 
-	CHECK(n_tokens == 2, EINVAL);
+	CHECK(n_tokens == 3, EINVAL);
 
 	strcpy(data->jmp_label, tokens[1]);
 
--
1.8.3.1


      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 13:57 Cristian Dumitrescu
2020-10-16 14:17 ` P, Venkata Suresh Kumar [this message]

Reply instructions:

You may reply publically 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=BYAPR11MB3077C34ECAC2E4FC1FBA16B699030@BYAPR11MB3077.namprd11.prod.outlook.com \
    --to=venkata.suresh.kumar.p@intel.com \
    --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

DPDK patches and discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/ public-inbox