From: Randy Dunlap <rdunlap@infradead.org>
To: Yingjie Wang <1075151112@qq.com>, linux-nvme@lists.infradead.org
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
kch@nvidia.com, hare@suse.de, corbet@lwn.net,
skhan@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] nvme-tcp: validate the TLS handshake timeout
Date: Tue, 27 Oct 2026 08:13:52 -0700 [thread overview]
Message-ID: <022548b6-607b-422c-b7db-5d95b0ba6b79@infradead.org> (raw)
In-Reply-To: <tencent_02EC3FD2E750D09B95ACA70091EE65DE0906@qq.com>
On 10/27/26 5:13 AM, Yingjie Wang wrote:
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index cc54d5f169f67..a5adbf58fb8f7 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -4801,6 +4801,11 @@ Kernel parameters
> Example:
> nvme.quirks=7710:2267:bogus_nid,^identify_cns-9900:7711:broken_msi
>
Maybe add "host" and "target" in the descriptions?
or something to clarify/distinguish them.
> + nvme_tcp.tls_handshake_timeout=
> + [NVME] TLS handshake timeout in seconds. Valid values
> + range from 0 to the smaller of UINT_MAX / 1000 and
> + MAX_JIFFY_OFFSET / HZ. Default: 10
> +
> nvmet_tcp.tls_handshake_timeout=
> [NVME] TLS handshake timeout in seconds. Valid values
> range from 0 to the smaller of UINT_MAX / 1000 and
--
~Randy
next prev parent reply other threads:[~2026-10-27 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1793103202.git.1075151112@qq.com>
2026-10-27 12:13 ` [PATCH v2 1/2] nvmet-tcp: " Yingjie Wang
2026-10-28 7:46 ` Hannes Reinecke
2026-10-27 12:13 ` [PATCH v2 2/2] nvme-tcp: " Yingjie Wang
2026-10-27 15:13 ` Randy Dunlap [this message]
2026-10-28 7:47 ` Hannes Reinecke
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=022548b6-607b-422c-b7db-5d95b0ba6b79@infradead.org \
--to=rdunlap@infradead.org \
--cc=1075151112@qq.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®