From: patchwork-bot+netdevbpf@kernel.org
To: Gal Pressman <gal@nvidia.com>
Cc: edumazet@google.com, kuba@kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, tariqt@nvidia.com, saeedm@nvidia.com
Subject: Re: [PATCH net 0/2] Couple of skb memory leak fixes
Date: Mon, 17 Jan 2022 13:10:09 +0000 [thread overview]
Message-ID: <164242500937.15907.17083517762593514431.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220117092733.6627-1-gal@nvidia.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 17 Jan 2022 11:27:31 +0200 you wrote:
> As discussed in:
> https://lore.kernel.org/netdev/20220102081253.9123-1-gal@nvidia.com/
>
> These are the two followup suggestions from Eric and Jakub.
> Patch #1 adds a sk_defer_free_flush() call to the kTLS splice_read
> handler.
> Patch #2 verifies the defer list is empty on socket destroy, and calls a
> defer free flush as well.
>
> [...]
Here is the summary with links:
- [net,1/2] net/tls: Fix another skb memory leak when running kTLS traffic
https://git.kernel.org/netdev/net/c/db094aa8140e
- [net,2/2] net: Flush deferred skb free on socket destroy
https://git.kernel.org/netdev/net/c/79074a72d335
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-01-17 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 9:27 [PATCH net 0/2] Couple of skb memory leak fixes Gal Pressman
2022-01-17 9:27 ` [PATCH net 1/2] net/tls: Fix another skb memory leak when running kTLS traffic Gal Pressman
2022-01-17 9:27 ` [PATCH net 2/2] net: Flush deferred skb free on socket destroy Gal Pressman
2022-01-23 9:50 ` Heiko Carstens
2022-01-23 9:53 ` Gal Pressman
2022-01-17 13:10 ` patchwork-bot+netdevbpf [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=164242500937.15907.17083517762593514431.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@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.