From: patchwork-bot+netdevbpf@kernel.org
To: Antoine Tenart <atenart@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
vladbu@nvidia.com, pabeni@redhat.com, pshelar@ovn.org,
daniel@iogearbox.net
Subject: Re: [PATCH net v2 0/2] net: fix issues when uncloning an skb dst+metadata
Date: Wed, 09 Feb 2022 12:00:09 +0000 [thread overview]
Message-ID: <164440800982.11178.11547441686052846325.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220207171319.157775-1-atenart@kernel.org>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 7 Feb 2022 18:13:17 +0100 you wrote:
> Hi,
>
> This fixes two issues when uncloning an skb dst+metadata in
> tun_dst_unclone; this was initially reported by Vlad Buslov[1]. Because
> of the memory leak fixed by patch 2, the issue in patch 1 never happened
> in practice.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: do not keep the dst cache when uncloning an skb dst and its metadata
https://git.kernel.org/netdev/net/c/cfc56f85e72f
- [net,v2,2/2] net: fix a memleak when uncloning an skb dst and its metadata
https://git.kernel.org/netdev/net/c/9eeabdf17fa0
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-02-09 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 17:13 [PATCH net v2 0/2] net: fix issues when uncloning an skb dst+metadata Antoine Tenart
2022-02-07 17:13 ` [PATCH net v2 1/2] net: do not keep the dst cache when uncloning an skb dst and its metadata Antoine Tenart
2022-02-07 18:17 ` Paolo Abeni
2022-02-07 17:13 ` [PATCH net v2 2/2] net: fix a memleak " Antoine Tenart
2022-02-09 12:00 ` 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=164440800982.11178.11547441686052846325.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=atenart@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.org \
--cc=vladbu@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.