From: Davide Caratti <dcaratti@redhat.com>
To: "David S. Miller" <davem@davemloft.net>,
Dave Watson <davejwatson@fb.com>,
Boris Pismenny <borisp@mellanox.com>,
Aviad Yehezkel <aviadye@mellanox.com>,
John Fastabend <john.fastabend@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org
Subject: [RFC PATCH net-next 0/2] net: extend INET_DIAG_INFO with information specific to TCP ULP
Date: Wed, 5 Jun 2019 17:39:21 +0200 [thread overview]
Message-ID: <cover.1559747691.git.dcaratti@redhat.com> (raw)
The current kernel does not provide any diagnostic tool, except
getsockopt(TCP_ULP), to know more about TCP sockets that have an upper
layer protocol (ULP) on top of them. This series extends the set of
information exported by INET_DIAG_INFO, to include data that are specific
to the ULP (and that might be meaningful for debug/testing purposes).
patch 1/2 extends INET_DIAG_INFO and allows knowing the ULP name for
each TCP socket that has done setsockopt(TCP_ULP) successfully.
kernel TLS is the only TCP ULP user at the moment: patch 2/2 extends kTLS
to let programs like 'ss' know the protocol version and the cipher in use.
Davide Caratti (2):
tcp: ulp: add functions to dump ulp-specific information
net: tls: export protocol version and cipher to socket diag
include/net/tcp.h | 3 +++
include/uapi/linux/inet_diag.h | 9 +++++++
include/uapi/linux/tls.h | 8 +++++++
net/ipv4/tcp_diag.c | 34 +++++++++++++++++++++++++--
net/tls/tls_main.c | 43 ++++++++++++++++++++++++++++++++++
5 files changed, 95 insertions(+), 2 deletions(-)
--
2.20.1
next reply other threads:[~2019-06-05 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 15:39 Davide Caratti [this message]
2019-06-05 15:39 ` [RFC PATCH net-next 1/2] tcp: ulp: add functions to dump ulp-specific information Davide Caratti
2019-06-05 23:14 ` Jakub Kicinski
2019-06-17 13:06 ` Davide Caratti
2019-06-17 17:41 ` Jakub Kicinski
2019-06-05 15:39 ` [RFC PATCH net-next 2/2] net: tls: export protocol version and cipher to socket diag Davide Caratti
2019-06-05 23:25 ` Jakub Kicinski
2019-06-17 16:04 ` Davide Caratti
2019-06-17 18:07 ` Jakub Kicinski
2019-06-06 7:07 ` Boris Pismenny
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.1559747691.git.dcaratti@redhat.com \
--to=dcaratti@redhat.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=john.fastabend@gmail.com \
--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).