From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Keith Busch <kbusch@kernel.org>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
zahavi.alon@gmail.com
Subject: Re: [PATCH] nvmet-tcp: Fix a possible UAF in queue intialization setup
Date: Thu, 5 Oct 2023 11:03:24 +0200 [thread overview]
Message-ID: <20231005090324.GA15643@lst.de> (raw)
In-Reply-To: <20231002105428.226515-1-sagi@grimberg.me>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2023-10-05 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 10:54 [PATCH] nvmet-tcp: Fix a possible UAF in queue intialization setup Sagi Grimberg
2023-10-03 3:39 ` Chaitanya Kulkarni
2023-10-03 8:28 ` Sagi Grimberg
2023-10-03 16:46 ` sj
2023-10-04 9:41 ` Sagi Grimberg
2023-10-04 12:25 ` Greg KH
2023-10-04 13:25 ` Sagi Grimberg
2023-10-04 17:32 ` SeongJae Park
2023-10-06 12:21 ` Sasha Levin
2023-10-05 9:03 ` Christoph Hellwig [this message]
2023-10-05 16:50 ` 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=20231005090324.GA15643@lst.de \
--to=hch@lst.de \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=zahavi.alon@gmail.com \
/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