From: patchwork-bot+netdevbpf@kernel•org
To: Paul Blakey <paulb@nvidia•com>
Cc: netdev@vger•kernel.org, eric.dumazet@gmail•com,
davem@davemloft•net, kuba@kernel•org, mika.penttila@nextfour•com,
ast@kernel•org, daniel@iogearbox•net, john.fastabend@gmail•com,
saeedm@nvidia•com, ozsh@nvidia•com, roid@nvidia•com,
vladbu@nvidia•com
Subject: Re: [PATCH net v3] skbuff: Release nfct refcount on napi stolen or re-used skbs
Date: Tue, 06 Jul 2021 17:30:04 +0000 [thread overview]
Message-ID: <162559260409.15284.11972045379958101158.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1625482491-17536-1-git-send-email-paulb@nvidia.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Mon, 5 Jul 2021 13:54:51 +0300 you wrote:
> When multiple SKBs are merged to a new skb under napi GRO,
> or SKB is re-used by napi, if nfct was set for them in the
> driver, it will not be released while freeing their stolen
> head state or on re-use.
>
> Release nfct on napi's stolen or re-used SKBs, and
> in gro_list_prepare, check conntrack metadata diff.
>
> [...]
Here is the summary with links:
- [net,v3] skbuff: Release nfct refcount on napi stolen or re-used skbs
https://git.kernel.org/netdev/net/c/8550ff8d8c75
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:[~2021-07-06 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 10:54 [PATCH net v3] skbuff: Release nfct refcount on napi stolen or re-used skbs Paul Blakey
2021-07-06 17:30 ` patchwork-bot+netdevbpf [this message]
2021-07-08 4:12 ` Florian Fainelli
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=162559260409.15284.11972045379958101158.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=mika.penttila@nextfour$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ozsh@nvidia$(echo .)com \
--cc=paulb@nvidia$(echo .)com \
--cc=roid@nvidia$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=vladbu@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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