From: Laurence Oberman <loberman@redhat.com>
To: Maurizio Lombardi <mlombard@redhat.com>, linux-nvme@lists.infradead.org
Cc: hch@lst.de, kbusch@kernel.org, sagi@grimberg.me, hare@suse.de,
mlombard@bsdbackstore.eu
Subject: Re: [PATCH V2] nvme-tcp: log TLS handshake failures at error level
Date: Wed, 02 Jul 2025 14:17:57 -0400 [thread overview]
Message-ID: <b30c3f7ff8082bfa9ff2ed2c65c4ed40c93933db.camel@redhat.com> (raw)
In-Reply-To: <20250702140629.70378-1-mlombard@redhat.com>
On Wed, 2025-07-02 at 16:06 +0200, Maurizio Lombardi wrote:
> Update the nvme_tcp_start_tls() function to use dev_err()
> instead of dev_dbg() when a TLS error is detected.
> This ensures that handshake failures are visible by default,
> aiding in debugging.
>
> Signed-off-by: Maurizio Lombardi <mlombard@redhat.com>
> ---
>
> v2: Hans suggests to print a dev_dbg() message
> if handshake is succesfull
>
> drivers/nvme/host/tcp.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
> index d924008c3949..9233f088fac8 100644
> --- a/drivers/nvme/host/tcp.c
> +++ b/drivers/nvme/host/tcp.c
> @@ -1745,9 +1745,14 @@ static int nvme_tcp_start_tls(struct nvme_ctrl
> *nctrl,
> qid, ret);
> tls_handshake_cancel(queue->sock->sk);
> } else {
> - dev_dbg(nctrl->device,
> - "queue %d: TLS handshake complete, error
> %d\n",
> - qid, queue->tls_err);
> + if (queue->tls_err) {
> + dev_err(nctrl->device,
> + "queue %d: TLS handshake complete,
> error %d\n",
> + qid, queue->tls_err);
> + } else {
> + dev_dbg(nctrl->device,
> + "queue %d: TLS handshake
> complete\n", qid);
> + }
> ret = queue->tls_err;
> }
> return ret;
V2 Looks good to me
If you need another review here it is
Reviewed-by: Laurence Oberman <loberman@redhat.com>
next prev parent reply other threads:[~2025-07-02 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 14:06 [PATCH V2] nvme-tcp: log TLS handshake failures at error level Maurizio Lombardi
2025-07-02 16:17 ` Hannes Reinecke
2025-07-02 18:17 ` Laurence Oberman [this message]
2025-07-03 11:43 ` Christoph Hellwig
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=b30c3f7ff8082bfa9ff2ed2c65c4ed40c93933db.camel@redhat.com \
--to=loberman@redhat.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@bsdbackstore.eu \
--cc=mlombard@redhat.com \
--cc=sagi@grimberg.me \
/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).