All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Shivam Kumar <kumar.shivam43666@gmail.com>,
	hch@lst.de, mlombard@arkamax.eu, kch@nvidia.com,
	linux-nvme@lists.infradead.org, kbusch@kernel.org,
	gregkh@linuxfoundation.org, security@kernel.org
Subject: Re: [PATCH v3] nvmet-tcp: set and enforce a default MDTS for TCP transport
Date: Mon, 11 May 2026 08:36:03 +0200	[thread overview]
Message-ID: <20260511063603.GB26080@lst.de> (raw)
In-Reply-To: <d06002f7-2da6-44bd-a0df-d9f2ef87a66c@grimberg.me>

On Sun, May 10, 2026 at 11:42:48PM +0300, Sagi Grimberg wrote:
> I think what we want is to limit the tcp to a sane limit similar to the 
> nvmet-rdma driver.

Agreed.

We might still need the early enforcement in Shivam's patch, though.



  reply	other threads:[~2026-05-11  6:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2026031805-stretch-skid-ae5b@gregkh>
2026-03-19  1:26 ` [PATCH] nvmet-tcp: bound sgl->length check in nvmet_tcp_map_data() Shivam Kumar
2026-03-19  7:59   ` Maurizio Lombardi
2026-03-19 18:00     ` Shivam Kumar
2026-03-20  7:48       ` Christoph Hellwig
2026-04-05 19:46         ` Shivam Kumar
2026-04-07  6:30           ` Christoph Hellwig
2026-04-08  6:30             ` Maurizio Lombardi
2026-04-09  6:08               ` Christoph Hellwig
2026-04-26 23:57                 ` Shivam Kumar
2026-04-27  0:44                 ` [PATCH v2] nvmet-tcp: set a default MDTS of 2 MiB for TCP transport Shivam Kumar
2026-04-28  6:07                   ` Maurizio Lombardi
2026-04-29  1:05                     ` Shivam Kumar
2026-05-08 20:39                     ` [PATCH v3] nvmet-tcp: set and enforce a default MDTS " Shivam Kumar
2026-05-10 20:42                       ` Sagi Grimberg
2026-05-11  6:36                         ` Christoph Hellwig [this message]
2026-05-11  8:01                           ` Sagi Grimberg
2026-05-11  8:04                             ` 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=20260511063603.GB26080@lst.de \
    --to=hch@lst.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.com \
    --cc=kumar.shivam43666@gmail.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mlombard@arkamax.eu \
    --cc=sagi@grimberg.me \
    --cc=security@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.