From: Hannes Reinecke <hare@suse.de>
To: Chuck Lever <cel@kernel.org>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: netdev@vger.kernel.org, kernel-tls-handshake@lists.linux.dev
Subject: Re: [PATCH net-next v1 7/7] net/handshake: Trace events for TLS Alert helpers
Date: Wed, 19 Jul 2023 09:53:15 +0200 [thread overview]
Message-ID: <b6e72739-02c4-9f06-1a0b-c49f679d1140@suse.de> (raw)
In-Reply-To: <168970690005.5330.12576672055397583164.stgit@oracle-102.nfsv4bat.org>
On 7/18/23 21:01, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> Add observability for the new TLS Alert infrastructure.
>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
> include/trace/events/handshake.h | 160 ++++++++++++++++++++++++++++++++++++++
> net/handshake/alert.c | 7 ++
> net/handshake/trace.c | 2
> 3 files changed, 169 insertions(+)
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, Frankenstr. 146, 90461 Nürnberg
Managing Directors: I. Totev, A. Myers, A. McDonald, M. B. Moerman
(HRB 36809, AG Nürnberg)
prev parent reply other threads:[~2023-07-19 7:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 18:58 [PATCH net-next v1 0/7] In-kernel support for the TLS Alert protocol Chuck Lever
2023-07-18 18:59 ` [PATCH net-next v1 1/7] net/tls: Move TLS protocol elements to a separate header Chuck Lever
2023-07-18 18:59 ` [PATCH net-next v1 2/7] net/tls: Add TLS Alert definitions Chuck Lever
2023-07-19 7:40 ` Hannes Reinecke
2023-07-18 19:00 ` [PATCH net-next v1 3/7] net/handshake: Add API for sending TLS Closure alerts Chuck Lever
2023-07-19 7:47 ` Hannes Reinecke
2023-07-19 13:24 ` Chuck Lever III
2023-07-18 19:00 ` [PATCH net-next v1 4/7] SUNRPC: Send TLS Closure alerts before closing a TCP socket Chuck Lever
2023-07-18 19:00 ` [PATCH net-next v1 5/7] net/handshake: Add helpers for parsing incoming TLS Alerts Chuck Lever
2023-07-19 7:52 ` Hannes Reinecke
2023-07-19 13:36 ` Chuck Lever III
2023-07-20 5:44 ` Hannes Reinecke
2023-07-20 14:22 ` Chuck Lever III
2023-07-18 19:01 ` [PATCH net-next v1 6/7] SUNRPC: Use new helpers to handle " Chuck Lever
2023-07-18 19:01 ` [PATCH net-next v1 7/7] net/handshake: Trace events for TLS Alert helpers Chuck Lever
2023-07-19 7:53 ` Hannes Reinecke [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=b6e72739-02c4-9f06-1a0b-c49f679d1140@suse.de \
--to=hare@suse.de \
--cc=cel@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=kuba@kernel.org \
--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 NNTP newsgroup(s).