From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeedm@nvidia.com>
Cc: kuba@kernel.org, netdev@vger.kernel.org, davem@davemloft.net,
maord@nvidia.com, paulb@nvidia.com
Subject: Re: [net v2 1/7] net/mlx5e: Fix modify header actions memory leak
Date: Sat, 07 Nov 2020 20:50:05 +0000 [thread overview]
Message-ID: <160478220555.18540.2570979913500058948.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201105202129.23644-2-saeedm@nvidia.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Thu, 5 Nov 2020 12:21:23 -0800 you wrote:
> From: Maor Dickman <maord@nvidia.com>
>
> Modify header actions are allocated during parse tc actions and only
> freed during the flow creation, however, on error flow the allocated
> memory is wrongly unfreed.
>
> Fix this by calling dealloc_mod_hdr_actions in __mlx5e_add_fdb_flow
> and mlx5e_add_nic_flow error flow.
>
> [...]
Here is the summary with links:
- [net,v2,1/7] net/mlx5e: Fix modify header actions memory leak
https://git.kernel.org/netdev/net/c/e68e28b4a9d7
- [net,v2,2/7] net/mlx5e: Protect encap route dev from concurrent release
https://git.kernel.org/netdev/net/c/78c906e430b1
- [net,v2,3/7] net/mlx5e: Use spin_lock_bh for async_icosq_lock
https://git.kernel.org/netdev/net/c/f42139ba4979
- [net,v2,4/7] net/mlx5: Fix deletion of duplicate rules
https://git.kernel.org/netdev/net/c/465e7baab6d9
- [net,v2,5/7] net/mlx5: E-switch, Avoid extack error log for disabled vport
https://git.kernel.org/netdev/net/c/ae3585944560
- [net,v2,6/7] net/mlx5e: Fix VXLAN synchronization after function reload
https://git.kernel.org/netdev/net/c/c5eb51adf06b
- [net,v2,7/7] net/mlx5e: Fix incorrect access of RCU-protected xdp_prog
https://git.kernel.org/netdev/net/c/1a50cf9a67ff
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2020-11-07 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 20:21 [pull request][net v2 0/7] mlx5 fixes 2020-11-03 Saeed Mahameed
2020-11-05 20:21 ` [net v2 1/7] net/mlx5e: Fix modify header actions memory leak Saeed Mahameed
2020-11-07 20:50 ` patchwork-bot+netdevbpf [this message]
2020-11-05 20:21 ` [net v2 2/7] net/mlx5e: Protect encap route dev from concurrent release Saeed Mahameed
2020-11-05 20:21 ` [net v2 3/7] net/mlx5e: Use spin_lock_bh for async_icosq_lock Saeed Mahameed
2020-11-05 20:21 ` [net v2 4/7] net/mlx5: Fix deletion of duplicate rules Saeed Mahameed
2020-11-05 20:21 ` [net v2 5/7] net/mlx5: E-switch, Avoid extack error log for disabled vport Saeed Mahameed
2020-11-05 20:21 ` [net v2 6/7] net/mlx5e: Fix VXLAN synchronization after function reload Saeed Mahameed
2020-11-05 20:21 ` [net v2 7/7] net/mlx5e: Fix incorrect access of RCU-protected xdp_prog Saeed Mahameed
2020-11-07 20:41 ` [pull request][net v2 0/7] mlx5 fixes 2020-11-03 Jakub Kicinski
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=160478220555.18540.2570979913500058948.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=maord@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=paulb@nvidia.com \
--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 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.