From: Keith Busch <kbusch@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
stable <stable@kernel.org>
Subject: Re: [PATCH] nvmet-tcp: Do not WARN on remotely-controlled oversized SGL allocations
Date: Thu, 30 Jul 2026 12:30:05 -0600 [thread overview]
Message-ID: <amuYLYQz8tj83K1d@kbusch-mbp> (raw)
In-Reply-To: <2026072944-express-relapsing-42d7@gregkh>
On Wed, Jul 29, 2026 at 07:39:09AM +0200, Greg Kroah-Hartman wrote:
> Thanks, I thought you all would allow stuff longer than 80 columns like
> the rest of the kernel does in places :)
The rest of the kernel on the wrong side of the 80 column limit is
wrong. :)
prev parent reply other threads:[~2026-07-30 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 20:03 [PATCH] nvmet-tcp: Do not WARN on remotely-controlled oversized SGL allocations Greg Kroah-Hartman
2026-07-28 17:14 ` Keith Busch
2026-07-29 5:39 ` Greg Kroah-Hartman
2026-07-30 18:30 ` Keith Busch [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=amuYLYQz8tj83K1d@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=stable@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.