DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ivan Malov <ivan.malov@oktetlabs.ru>,
Cc: Andy Moreton <amoreton@xilinx.com>
Subject: Re: [dpdk-dev] [PATCH] net/sfc: fix double free on encap. transfer flow rule path
Date: Tue, 17 Nov 2020 13:34:50 +0000	[thread overview]
Message-ID: <b0f14e5f-05c7-5c88-89e9-caf5dacaf21b@intel.com> (raw)
In-Reply-To: <33fdd341-871f-9d67-e2b1-823030aa05c0@oktetlabs.ru>

On 11/17/2020 7:39 AM, Andrew Rybchenko wrote:
> On 11/16/20 10:23 PM, Ivan Malov wrote:
>> Don't free the outer match spec by its pointer in the parsing context
>> if it has already been tracked by an entry in the outer rule registry.
>> Fixes: dadff137931c ("net/sfc: support encap flow items in transfer rules")
>> Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>

Applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2020-11-17 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 19:23 Ivan Malov
2020-11-17  7:39 ` Andrew Rybchenko
2020-11-17 13:34   ` Ferruh Yigit [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b0f14e5f-05c7-5c88-89e9-caf5dacaf21b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=amoreton@xilinx.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ivan.malov@oktetlabs.ru \


* 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).