From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, kbusch@kernel.org,
sagi@grimberg.me, gjoyce@linux.ibm.com, chaitanyak@nvidia.com
Subject: Re: [PATCH v2 2/2] nvmet: fix use-after-free in passthru I/O hotpath
Date: Thu, 5 Nov 2026 08:56:36 +0900 [thread overview]
Message-ID: <auvFmbUwmva581_7@shinmob> (raw)
In-Reply-To: <98022e84-32f6-430e-899b-1f5cd9777183@linux.ibm.com>
On Nov 03, 2026 / 06:49, Nilay Shroff wrote:
[...]
> Based on the above, I prepared a patch[1] to fix this issue. May I ask you to
> validate this patch on your system? If this works for you then I'll send out a
> formal patch.
>
> [1]
(snip)
Nilay, thank you for the action. I validated your patch, and confirmed it works!
The patch avoided the hang. I also run whole blktests in my environment and
observed no regression. When you post the patch, feel free to add,
Tested-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
next prev parent reply other threads:[~2026-11-04 23:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 11:26 [PATCH v2 0/2] nvmet: passthru cleanup and fixup I/O hotpath Nilay Shroff
2026-09-29 11:26 ` [PATCH v2 1/2] nvmet: introduce struct nvmet_passthru Nilay Shroff
2026-10-13 14:36 ` Christoph Hellwig
2026-09-29 11:26 ` [PATCH v2 2/2] nvmet: fix use-after-free in passthru I/O hotpath Nilay Shroff
2026-10-13 14:36 ` Christoph Hellwig
2026-11-02 10:49 ` Shin'ichiro Kawasaki
2026-11-03 1:19 ` Nilay Shroff
2026-11-04 23:56 ` Shin'ichiro Kawasaki [this message]
2026-10-13 15:35 ` [PATCH v2 0/2] nvmet: passthru cleanup and fixup " Keith Busch
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=auvFmbUwmva581_7@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=chaitanyak@nvidia.com \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.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 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.