netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Harris <jgh@exim.org>
To: netdev@vger.kernel.org
Cc: Jeremy Harris <jgh@exim.org>
Subject: [RFC PATCH net-next 0/2] TCP: Fast-Open observability
Date: Thu, 13 Mar 2025 14:45:49 +0000	[thread overview]
Message-ID: <cover.1741877016.git.jgh@exim.org> (raw)

Whether TCP Fast Open was used, or not, for a connection is not reliably
observable by an accepting application.

Fix this by noting during SYN processing that an acceptable Fast Open option
was used, and provide this to userland via getsockopt TCP_INFO.

Jeremy Harris (2):
  TCP: note received valid-cookie Fast Open option
  TCP: pass accepted-TFO indication through getsockopt

 include/linux/tcp.h      | 3 ++-
 include/uapi/linux/tcp.h | 1 +
 net/ipv4/tcp.c           | 2 ++
 net/ipv4/tcp_fastopen.c  | 1 +
 4 files changed, 6 insertions(+), 1 deletion(-)


base-commit: 5a1dddd2944492edb1e61c5db1cc386e5419fcf4
-- 
2.48.1


             reply	other threads:[~2025-03-13 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 14:45 Jeremy Harris [this message]
2025-03-13 14:45 ` [RFC PATCH net-next 1/2] TCP: note received valid-cookie Fast Open option Jeremy Harris
2025-03-13 14:45 ` [RFC PATCH net-next 2/2] TCP: pass accepted-TFO indication through getsockopt Jeremy Harris

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=cover.1741877016.git.jgh@exim.org \
    --to=jgh@exim.org \
    --cc=netdev@vger.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 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 NNTP newsgroup(s).