DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Morrissey, Sean" <sean.morrissey@intel.com>
Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>,
	dev@dpdk.org, "stable@dpdk.org" <stable@dpdk.org>,
	"Chen, LingliX" <linglix.chen@intel.com>
Subject: Re: [PATCH v1] examples/l3fwd: fix core dump after packet match
Date: Mon, 10 Oct 2022 23:51:49 +0200	[thread overview]
Message-ID: <3744027.FjKLVJYuhi@thomas> (raw)
In-Reply-To: <SJ0PR11MB48930BD3C4A26CFAC140FBDF905E9@SJ0PR11MB4893.namprd11.prod.outlook.com>

> > This patch fixes a core dump which occurs on 32-bit-builds after sending a
> > matched packet due to overrunning an array.
> > 
> > Fixes: 6de0ea50e9b9 ("examples/l3fwd: merge l3fwd-acl example")
> > Cc: sean.morrissey@intel.com
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: Sean Morrissey <sean.morrissey@intel.com>
> Tested-by: Lingli Chen <linglix.chen@intel.com>

Applied, thanks.



      reply	other threads:[~2022-10-10 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 11:33 Sean Morrissey
2022-09-21 18:14 ` Medvedkin, Vladimir
2022-10-08  3:11 ` Chen, LingliX
2022-10-10 21:51   ` Thomas Monjalon [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=3744027.FjKLVJYuhi@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=linglix.chen@intel.com \
    --cc=sean.morrissey@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).