From: patchwork-bot+netdevbpf@kernel.org
To: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Cc: mptcp@lists.linux.dev, edumazet@google.com, davem@davemloft.net,
dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com,
martineau@kernel.org, geliang@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: socket option to check for MPTCP fallback to TCP
Date: Mon, 13 May 2024 22:00:30 +0000 [thread overview]
Message-ID: <171563763083.31066.11558902540602032643.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240509-upstream-net-next-20240509-mptcp-tcp_is_mptcp-v1-1-f846df999202@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 09 May 2024 20:10:10 +0200 you wrote:
> A way for an application to know if an MPTCP connection fell back to TCP
> is to use getsockopt(MPTCP_INFO) and look for errors. The issue with
> this technique is that the same errors -- EOPNOTSUPP (IPv4) and
> ENOPROTOOPT (IPv6) -- are returned if there was a fallback, *or* if the
> kernel doesn't support this socket option. The userspace then has to
> look at the kernel version to understand what the errors mean.
>
> [...]
Here is the summary with links:
- [net-next] tcp: socket option to check for MPTCP fallback to TCP
https://git.kernel.org/netdev/net-next/c/c084ebd77a00
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-05-13 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 18:10 [PATCH net-next] tcp: socket option to check for MPTCP fallback to TCP Matthieu Baerts (NGI0)
2024-05-13 22:00 ` 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=171563763083.31066.11558902540602032643.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).