From: Yonghong Song <yonghong.song@linux•dev>
To: Geliang Tang <geliang.tang@suse•com>,
Alexei Starovoitov <ast@kernel•org>,
Daniel Borkmann <daniel@iogearbox•net>,
Andrii Nakryiko <andrii@kernel•org>,
Martin KaFai Lau <martin.lau@linux•dev>,
Song Liu <song@kernel•org>, Yonghong Song <yhs@fb•com>,
John Fastabend <john.fastabend@gmail•com>,
KP Singh <kpsingh@kernel•org>,
Stanislav Fomichev <sdf@google•com>, Hao Luo <haoluo@google•com>,
Jiri Olsa <jolsa@kernel•org>,
Florent Revest <revest@chromium•org>,
Brendan Jackman <jackmanb@chromium•org>,
Matthieu Baerts <matthieu.baerts@tessares•net>,
Mat Martineau <martineau@kernel•org>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
John Johansen <john.johansen@canonical•com>,
Paul Moore <paul@paul-moore•com>,
James Morris <jmorris@namei•org>,
"Serge E. Hallyn" <serge@hallyn•com>,
Stephen Smalley <stephen.smalley.work@gmail•com>,
Eric Paris <eparis@parisplace•org>,
Mykola Lysenko <mykolal@fb•com>, Shuah Khan <shuah@kernel•org>,
Simon Horman <horms@kernel•org>
Cc: bpf@vger•kernel.org, netdev@vger•kernel.org,
mptcp@lists•linux.dev, apparmor@lists•ubuntu.com,
linux-security-module@vger•kernel.org, selinux@vger•kernel.org,
linux-kselftest@vger•kernel.org
Subject: Re: [PATCH bpf-next v10 1/5] bpf: Add update_socket_protocol hook
Date: Thu, 3 Aug 2023 21:28:00 -0700 [thread overview]
Message-ID: <9c0782dc-fdca-0d1c-cff4-ae1d6d719be8@linux.dev> (raw)
In-Reply-To: <079989b68ddded562b9f2149cc50642072575001.1691113640.git.geliang.tang@suse.com>
On 8/3/23 6:55 PM, Geliang Tang wrote:
> Add a hook named update_socket_protocol in __sys_socket(), for bpf
> progs to attach to and update socket protocol. One user case is to
> force legacy TCP apps to create and use MPTCP sockets instead of
> TCP ones.
>
> Define a mod_ret set named bpf_mptcp_fmodret_ids, add the hook
> update_socket_protocol into this set, and register it in
> bpf_mptcp_kfunc_init().
>
> Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/79
> Acked-by: Matthieu Baerts <matthieu.baerts@tessares•net>
> Signed-off-by: Geliang Tang <geliang.tang@suse•com>
Acked-by: Yonghong Song <yonghong.song@linux•dev>
next prev parent reply other threads:[~2023-08-04 4:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 1:55 [PATCH bpf-next v10 0/5] bpf: Force to MPTCP Geliang Tang
2023-08-04 1:55 ` [PATCH bpf-next v10 1/5] bpf: Add update_socket_protocol hook Geliang Tang
2023-08-04 4:28 ` Yonghong Song [this message]
2023-08-04 1:55 ` [PATCH bpf-next v10 2/5] selftests/bpf: Use random netns name for mptcp Geliang Tang
2023-08-04 1:55 ` [PATCH bpf-next v10 3/5] selftests/bpf: Add two mptcp netns helpers Geliang Tang
2023-08-04 1:55 ` [PATCH bpf-next v10 4/5] selftests/bpf: Drop unneeded checks for mptcp Geliang Tang
2023-08-04 4:31 ` Yonghong Song
2023-08-04 1:55 ` [PATCH bpf-next v10 5/5] selftests/bpf: Add mptcpify test Geliang Tang
2023-08-04 4:43 ` Yonghong Song
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=9c0782dc-fdca-0d1c-cff4-ae1d6d719be8@linux.dev \
--to=yonghong.song@linux$(echo .)dev \
--cc=andrii@kernel$(echo .)org \
--cc=apparmor@lists$(echo .)ubuntu.com \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=eparis@parisplace$(echo .)org \
--cc=geliang.tang@suse$(echo .)com \
--cc=haoluo@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jackmanb@chromium$(echo .)org \
--cc=jmorris@namei$(echo .)org \
--cc=john.fastabend@gmail$(echo .)com \
--cc=john.johansen@canonical$(echo .)com \
--cc=jolsa@kernel$(echo .)org \
--cc=kpsingh@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux-security-module@vger$(echo .)kernel.org \
--cc=martin.lau@linux$(echo .)dev \
--cc=martineau@kernel$(echo .)org \
--cc=matthieu.baerts@tessares$(echo .)net \
--cc=mptcp@lists$(echo .)linux.dev \
--cc=mykolal@fb$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=paul@paul-moore$(echo .)com \
--cc=revest@chromium$(echo .)org \
--cc=sdf@google$(echo .)com \
--cc=selinux@vger$(echo .)kernel.org \
--cc=serge@hallyn$(echo .)com \
--cc=shuah@kernel$(echo .)org \
--cc=song@kernel$(echo .)org \
--cc=stephen.smalley.work@gmail$(echo .)com \
--cc=yhs@fb$(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