netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Davide Caratti <dcaratti@redhat.com>
Cc: borisp@mellanox.com, Eric Dumazet <eric.dumazet@gmail.com>,
	aviadye@mellanox.com, davejwatson@fb.com, davem@davemloft.net,
	john.fastabend@gmail.com,
	Matthieu Baerts <matthieu.baerts@tessares.net>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 3/3] net: tls: export protocol version, cipher, tx_conf/rx_conf to socket diag
Date: Fri, 30 Aug 2019 15:45:23 -0700	[thread overview]
Message-ID: <20190830154523.1ee70d81@cakuba.netronome.com> (raw)
In-Reply-To: <39ad297f2b1f129b26c4a3461a1ae443d836da52.1567158431.git.dcaratti@redhat.com>

On Fri, 30 Aug 2019 12:25:49 +0200, Davide Caratti wrote:
> When an application configures kernel TLS on top of a TCP socket, it's
> now possible for inet_diag_handler() to collect information regarding the
> protocol version, the cipher type and TX / RX configuration, in case
> INET_DIAG_INFO is requested.
> 
> Signed-off-by: Davide Caratti <dcaratti@redhat.com>

Reviewed-by: Jakub Kicinski <jakub.kicinski@netronome.com>

Thank you!

  reply	other threads:[~2019-08-30 22:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30 10:25 [PATCH net-next v3 0/3] net: tls: add socket diag Davide Caratti
2019-08-30 10:25 ` [PATCH net-next v3 1/3] net/tls: use RCU protection on icsk->icsk_ulp_data Davide Caratti
2019-08-30 10:25 ` [PATCH net-next v3 2/3] tcp: ulp: add functions to dump ulp-specific information Davide Caratti
2019-08-30 10:25 ` [PATCH net-next v3 3/3] net: tls: export protocol version, cipher, tx_conf/rx_conf to socket diag Davide Caratti
2019-08-30 22:45   ` Jakub Kicinski [this message]
2019-09-01  6:44 ` [PATCH net-next v3 0/3] net: tls: add " David Miller

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=20190830154523.1ee70d81@cakuba.netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=aviadye@mellanox.com \
    --cc=borisp@mellanox.com \
    --cc=davejwatson@fb.com \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=eric.dumazet@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=matthieu.baerts@tessares.net \
    --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).