All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Akhil Goyal <gakhil@marvell.com>
Cc: <dev@dpdk.org>, <hemant.agrawal@nxp.com>, <vattunuru@marvell.com>,
	<stable@dpdk.org>
Subject: Re: [PATCH v2] test/security: fix buffer leaks in error path
Date: Tue, 31 Oct 2023 08:47:32 -0700	[thread overview]
Message-ID: <20231031084732.6ffba4c1@fedora> (raw)
In-Reply-To: <20231031064446.150191-1-gakhil@marvell.com>

On Tue, 31 Oct 2023 12:14:46 +0530
Akhil Goyal <gakhil@marvell.com> wrote:

> From: Akhil Goyal <gakhil@marvell.com>
> To: <dev@dpdk.org>
> CC: <stephen@networkplumber.org>, <hemant.agrawal@nxp.com>,         <vattunuru@marvell.com>, Akhil Goyal <gakhil@marvell.com>,         <stable@dpdk.org>
> Subject: [PATCH v2] test/security: fix buffer leaks in error path
> Date: Tue, 31 Oct 2023 12:14:46 +0530
> X-Mailer: git-send-email 2.25.1
> 
> In case of failure of a test in macsec autotest,
> the buffers were not getting cleaned.
> Added appropriate code to clean the buffers.
> 
> Fixes: 993ea577a006 ("test/security: add inline MACsec cases")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Akhil Goyal <gakhil@marvell.com>

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

  parent reply	other threads:[~2023-10-31 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 17:33 [PATCH] test/security: fix buffer leaks in error path Akhil Goyal
2023-08-25 11:22 ` Hemant Agrawal
2023-09-19  6:33   ` [EXT] " Akhil Goyal
2023-09-19 14:58 ` Stephen Hemminger
2023-09-19 19:17   ` [EXT] " Akhil Goyal
2023-10-31  6:44 ` [PATCH v2] " Akhil Goyal
2023-10-31 13:56   ` Hemant Agrawal
2023-10-31 15:47   ` Stephen Hemminger [this message]
2023-10-31 17:59     ` [EXT] " Akhil Goyal

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=20231031084732.6ffba4c1@fedora \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=stable@dpdk.org \
    --cc=vattunuru@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.