From: patchwork-bot+netdevbpf@kernel•org
To: Sewook Seo <ssewook@gmail•com>
Cc: sewookseo@google•com, netdev@vger•kernel.org,
davem@davemloft•net, yoshfuji@linux-ipv6•org, dsahern@kernel•org,
kuba@kernel•org, pabeni@redhat•com, maze@google•com,
edumazet@google•com, steffen.klassert@secunet•com,
seheele@google•com
Subject: Re: [PATCH v5 net-next] net: Find dst with sk's xfrm policy not ctl_sk
Date: Mon, 11 Jul 2022 13:10:12 +0000 [thread overview]
Message-ID: <165754501239.30308.12114903372158946352.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220707100139.3748417-1-ssewook@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft•net>:
On Thu, 7 Jul 2022 10:01:39 +0000 you wrote:
> From: sewookseo <sewookseo@google•com>
>
> If we set XFRM security policy by calling setsockopt with option
> IPV6_XFRM_POLICY, the policy will be stored in 'sock_policy' in 'sock'
> struct. However tcp_v6_send_response doesn't look up dst_entry with the
> actual socket but looks up with tcp control socket. This may cause a
> problem that a RST packet is sent without ESP encryption & peer's TCP
> socket can't receive it.
> This patch will make the function look up dest_entry with actual socket,
> if the socket has XFRM policy(sock_policy), so that the TCP response
> packet via this function can be encrypted, & aligned on the encrypted
> TCP socket.
>
> [...]
Here is the summary with links:
- [v5,net-next] net: Find dst with sk's xfrm policy not ctl_sk
https://git.kernel.org/netdev/net-next/c/e22aa1486668
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-07-11 13:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 20:22 [PATCH] net-tcp: Find dst with sk's xfrm policy not ctl_sk Sewook Seo
2022-06-22 2:01 ` Eric Dumazet
2022-07-01 15:44 ` [PATCH v2] " Sewook Seo
2022-07-05 8:25 ` Paolo Abeni
2022-07-06 3:10 ` 서세욱
2022-07-06 14:01 ` Paolo Abeni
2022-07-06 14:07 ` Eric Dumazet
2022-07-05 9:04 ` Eric Dumazet
2022-07-06 3:09 ` 서세욱
2022-07-03 13:41 ` [net] fe1d0fd632: canonical_address#:#[##] kernel test robot
2022-07-06 6:32 ` [PATCH v3 net-next] net: Find dst with sk's xfrm policy not ctl_sk Sewook Seo
2022-07-06 7:19 ` Eric Dumazet
2022-07-06 14:59 ` David Ahern
2022-07-06 21:30 ` 서세욱
2022-07-07 5:40 ` [PATCH v4 " Sewook Seo
2022-07-07 7:41 ` Eric Dumazet
2022-07-07 10:01 ` [PATCH v5 " Sewook Seo
2022-07-11 8:42 ` Steffen Klassert
2022-07-11 8:59 ` Eric Dumazet
2022-07-11 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=165754501239.30308.12114903372158946352.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=maze@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=seheele@google$(echo .)com \
--cc=sewookseo@google$(echo .)com \
--cc=ssewook@gmail$(echo .)com \
--cc=steffen.klassert@secunet$(echo .)com \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/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