From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
jmaloy@redhat.com, ying.xue@windriver.com,
tuong.t.lien@dektech.com.au, davem@davemloft.net,
kuba@kernel.org
Subject: Re: [PATCH net-next] tipc: delete the unlikely branch in tipc_aead_encrypt
Date: Fri, 26 Nov 2021 05:10:09 +0000 [thread overview]
Message-ID: <163790340963.15462.7702014656238817068.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <47a478da0b6095b76e3cbe7a75cbd25d9da1df9a.1637773872.git.lucien.xin@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 24 Nov 2021 12:11:12 -0500 you wrote:
> When a skb comes to tipc_aead_encrypt(), it's always linear. The
> unlikely check 'skb_cloned(skb) && tailen <= skb_tailroom(skb)'
> can completely be taken care of in skb_cow_data() by the code
> in branch "if (!skb_has_frag_list())".
>
> Also, remove the 'TODO:' annotation, as the pages in skbs are not
> writable, see more on commit 3cf4375a0904 ("tipc: do not write
> skb_shinfo frags when doing decrytion").
>
> [...]
Here is the summary with links:
- [net-next] tipc: delete the unlikely branch in tipc_aead_encrypt
https://git.kernel.org/netdev/net-next/c/0c51dffcc8a2
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:[~2021-11-26 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 17:11 [PATCH net-next] tipc: delete the unlikely branch in tipc_aead_encrypt Xin Long
2021-11-26 5: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=163790340963.15462.7702014656238817068.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jmaloy@redhat.com \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--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 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.