From: Jakub Kicinski <kuba@kernel.org>
To: Saeed Mahameed <saeed@kernel.org>
Cc: patchwork-bot+netdevbpf@kernel.org,
Leon Romanovsky <leon@kernel.org>,
davem@davemloft.net, phaddad@nvidia.com, edumazet@google.com,
linux-rdma@vger.kernel.org, markzhang@nvidia.com,
netdev@vger.kernel.org, pabeni@redhat.com, raeds@nvidia.com,
saeedm@nvidia.com
Subject: Re: [PATCH net v1] net/mlx5: Fix memory leak in IPsec RoCE creation
Date: Thu, 23 Feb 2023 16:14:05 -0800 [thread overview]
Message-ID: <20230223161405.7dc7843b@kernel.org> (raw)
In-Reply-To: <Y/ftZTzCkyW/vn4Z@x130>
On Thu, 23 Feb 2023 14:49:09 -0800 Saeed Mahameed wrote:
> On 23 Feb 10:30, patchwork-bot+netdevbpf@kernel.org wrote:
> >Hello:
> >
> >This patch was applied to netdev/net.git (master)
> >by Paolo Abeni <pabeni@redhat.com>:
> >
> >On Wed, 22 Feb 2023 11:06:40 +0200 you wrote:
> >> From: Patrisious Haddad <phaddad@nvidia.com>
> >>
> >> During IPsec RoCE TX creation a struct for the flow group creation is
> >> allocated, but never freed. Free that struct once it is no longer in use.
> >>
> >> Fixes: 22551e77e550 ("net/mlx5: Configure IPsec steering for egress RoCEv2 traffic")
> >> Signed-off-by: Patrisious Haddad <phaddad@nvidia.com>
> >> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> >>
> >> [...]
> >
> >Here is the summary with links:
> > - [net,v1] net/mlx5: Fix memory leak in IPsec RoCE creation
> > https://git.kernel.org/netdev/net/c/c749e3f82a15
> >
>
> hmm, I don't see this one in net branch, should i resubmit via my queue?
It's there:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=c749e3f82a15e10a798bb55f60368ee102c793cb
But keep in mind that master is gone (long live main).
prev parent reply other threads:[~2023-02-24 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 9:06 [PATCH net v1] net/mlx5: Fix memory leak in IPsec RoCE creation Leon Romanovsky
2023-02-23 10:30 ` patchwork-bot+netdevbpf
2023-02-23 22:49 ` Saeed Mahameed
2023-02-24 0:14 ` Jakub Kicinski [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=20230223161405.7dc7843b@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=markzhang@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=phaddad@nvidia.com \
--cc=raeds@nvidia.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.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).