From: patchwork-bot+netdevbpf@kernel.org
To: Kui-Feng Lee <kuifeng@meta.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
song@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v3 0/2] Enable bpf_setsockopt() on ktls enabled sockets.
Date: Wed, 25 Jan 2023 23:20:17 +0000 [thread overview]
Message-ID: <167468881702.27315.585615973493315531.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230125201608.908230-1-kuifeng@meta.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 25 Jan 2023 12:16:06 -0800 you wrote:
> This patchset implements a change to bpf_setsockopt() which allows
> ktls enabled sockets to be used with the SOL_TCP level. This is
> necessary as when ktls is enabled, it changes the function pointer of
> setsockopt of the socket, which bpf_setsockopt() checks in order to
> make sure that the socket is a TCP socket. Checking sk_protocol
> instead of the function pointer will ensure that bpf_setsockopt() with
> the SOL_TCP level still works on sockets with ktls enabled.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf: Check the protocol of a sock to agree the calls to bpf_setsockopt().
https://git.kernel.org/bpf/bpf-next/c/2ab42c7b871f
- [bpf-next,v3,2/2] selftests/bpf: Calls bpf_setsockopt() on a ktls enabled socket.
https://git.kernel.org/bpf/bpf-next/c/d1246f936023
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:[~2023-01-25 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 20:16 [PATCH bpf-next v3 0/2] Enable bpf_setsockopt() on ktls enabled sockets Kui-Feng Lee
2023-01-25 20:16 ` [PATCH bpf-next v3 1/2] bpf: Check the protocol of a sock to agree the calls to bpf_setsockopt() Kui-Feng Lee
2023-01-25 20:16 ` [PATCH bpf-next v3 2/2] selftests/bpf: Calls bpf_setsockopt() on a ktls enabled socket Kui-Feng Lee
2023-01-25 23:17 ` Martin KaFai Lau
2023-01-26 18:12 ` Kui-Feng Lee
2023-01-25 23: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=167468881702.27315.585615973493315531.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=song@kernel.org \
/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.