From: Christoph Hellwig <hch@lst.de>
To: Shivam Kumar <kumar.shivam43666@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
gregkh@linuxfoundation.org, security@kernel.org,
sagi@grimberg.me, kch@nvidia.com, linux-nvme@lists.infradead.org,
kbusch@kernel.org
Subject: Re: [PATCH] nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path
Date: Tue, 7 Apr 2026 08:31:39 +0200 [thread overview]
Message-ID: <20260407063139.GB7036@lst.de> (raw)
In-Reply-To: <CA+ysrS+Uht6pXJ3odiyGccZ7HrR+WvtrHexNkTB1Gvy=Uxw79w@mail.gmail.com>
On Sun, Apr 05, 2026 at 03:54:24PM -0400, Shivam Kumar wrote:
> Hi all,
>
> Just following up on this patch.
> Please let me know if there are any concerns or if any changes are needed.
Well, if we can't get people more familiar with TCP to look over it
there's not much we can do but include it.
next prev parent reply other threads:[~2026-04-07 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+ysrS+QrbGfOLk=e0=PZ-py-KO_xZgn827nEg7mh7hGhdUAAw@mail.gmail.com>
[not found] ` <2026031827-carving-overdrawn-5b1f@gregkh>
2026-03-18 22:56 ` [PATCH] nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path Shivam Kumar
2026-03-20 7:46 ` Christoph Hellwig
2026-04-05 19:54 ` Shivam Kumar
2026-04-07 6:31 ` Christoph Hellwig [this message]
2026-04-07 14:26 ` Keith Busch
[not found] ` <CA+ysrSLcSJSgEC7i0GYXPiRY9sbbyEGT60Nh1SJ6PqXWENgSOw@mail.gmail.com>
[not found] ` <CA+ysrSL+3YVGvTKhJ=jL92XZPwjoDpt5D2BK-HeCU975vO-fCQ@mail.gmail.com>
[not found] ` <CA+ysrSJQ2tDiB=zL+GwF=ckhmO62v6GC2bWVUVVDVn7d8Km1mw@mail.gmail.com>
2026-03-25 4:29 ` [Bug Report] nvmet-tcp: unbalanced percpu_ref_put on data digest error after nvmet_req_init failure causes refcount underflow, use-after-free, and permanent workqueue deadlock Chaitanya Kulkarni
2026-04-05 19:55 ` Shivam Kumar
2026-04-06 4:23 ` Chaitanya Kulkarni
2026-04-06 19:25 ` Shivam Kumar
2026-04-06 22:16 ` Chaitanya Kulkarni
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=20260407063139.GB7036@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox