From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, jmaloy@redhat.com, ying.xue@windriver.com,
tung.q.nguyen@dektech.com.au, tuong.t.lien@dektech.com.au
Subject: Re: [PATCH net] tipc: force a dst refcount before doing decryption
Date: Tue, 18 Jun 2024 13:20:28 +0000 [thread overview]
Message-ID: <171871682845.4510.4691473810061988623.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <fbe3195fad6997a4eec62d9bf076b2ad03ac336b.1718476040.git.lucien.xin@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 15 Jun 2024 14:27:20 -0400 you wrote:
> As it says in commit 3bc07321ccc2 ("xfrm: Force a dst refcount before
> entering the xfrm type handlers"):
>
> "Crypto requests might return asynchronous. In this case we leave the
> rcu protected region, so force a refcount on the skb's destination
> entry before we enter the xfrm type input/output handlers."
>
> [...]
Here is the summary with links:
- [net] tipc: force a dst refcount before doing decryption
https://git.kernel.org/netdev/net/c/2ebe8f840c74
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:[~2024-06-18 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-15 18:27 [PATCH net] tipc: force a dst refcount before doing decryption Xin Long
2024-06-18 13:20 ` 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=171871682845.4510.4691473810061988623.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tung.q.nguyen@dektech.com.au \
--cc=tuong.t.lien@dektech.com.au \
--cc=ying.xue@windriver.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).