Re: [PATCH v2 0/4] nvme: protect against possible request reference after completion

[PATCH v2 0/4] nvme: protect against possible request reference after completion · Sagi Grimberg <sagi@grimberg.me> · 2021-05-19
[PATCH v2 1/4] params: lift param_set_uint_minmax to common code · Sagi Grimberg <sagi@grimberg.me> · 2021-05-19
Re: [PATCH v2 1/4] params: lift param_set_uint_minmax to common code · Chaitanya Kulkarni <hidden> · 2021-05-19
Re: [PATCH v2 1/4] params: lift param_set_uint_minmax to common code · Christoph Hellwig <hch@lst.de> · 2021-05-20
[PATCH v2 2/4] nvme-pci: limit maximum queue depth to 4095 · Sagi Grimberg <sagi@grimberg.me> · 2021-05-19
Re: [PATCH v2 2/4] nvme-pci: limit maximum queue depth to 4095 · Chaitanya Kulkarni <hidden> · 2021-05-19
Re: [PATCH v2 2/4] nvme-pci: limit maximum queue depth to 4095 · Hannes Reinecke <hare@suse.de> · 2021-05-26
[PATCH v2 3/4] nvme-tcp: don't check blk_mq_tag_to_rq when receiving pdu data · Sagi Grimberg <sagi@grimberg.me> · 2021-05-19
Re: [PATCH v2 3/4] nvme-tcp: don't check blk_mq_tag_to_rq when receiving pdu data · Hannes Reinecke <hare@suse.de> · 2021-05-26
[PATCH v2 4/4] nvme: code command_id with a genctr for use-after-free validation · Sagi Grimberg <sagi@grimberg.me> · 2021-05-19
Re: [PATCH v2 4/4] nvme: code command_id with a genctr for use-after-free validation · Daniel Wagner <hidden> · 2021-05-20
Re: [PATCH v2 4/4] nvme: code command_id with a genctr for use-after-free validation · Max Gurtovoy <mgurtovoy@nvidia.com> · 2021-05-25
Re: [PATCH v2 4/4] nvme: code command_id with a genctr for use-after-free validation · Keith Busch <kbusch@kernel.org> · 2021-05-26
Re: [PATCH v2 4/4] nvme: code command_id with a genctr for use-after-free validation · Chaitanya Kulkarni <hidden> · 2021-05-26
Re: [PATCH v2 4/4] nvme: code command_id with a genctr for use-after-free validation · Sagi Grimberg <sagi@grimberg.me> · 2021-05-26
Re: [PATCH v2 4/4] nvme: code command_id with a genctr for use-after-free validation · Hannes Reinecke <hare@suse.de> · 2021-05-26
Re: [PATCH v2 4/4] nvme: code command_id with a genctr for use-after-free validation · Max Gurtovoy <mgurtovoy@nvidia.com> · 2021-05-26
Re: [PATCH v2 4/4] nvme: code command_id with a genctr for use-after-free validation · Hannes Reinecke <hare@suse.de> · 2021-05-26
Re: [PATCH v2 0/4] nvme: protect against possible request reference after completion · Sagi Grimberg <sagi@grimberg.me> · 2021-06-16
Re: [PATCH v2 0/4] nvme: protect against possible request reference after completion · Keith Busch <kbusch@kernel.org> · 2021-06-16
Re: [PATCH v2 0/4] nvme: protect against possible request reference after completion · Sagi Grimberg <sagi@grimberg.me> · 2021-06-16
Re: [PATCH v2 0/4] nvme: protect against possible request reference after completion · Daniel Wagner <hidden> · 2021-07-01
Re: [PATCH v2 0/4] nvme: protect against possible request reference after completion · Christoph Hellwig <hch@lst.de> · 2021-07-01
Re: [PATCH v2 0/4] nvme: protect against possible request reference after completion · Daniel Wagner <hidden> · 2021-07-08
Re: [PATCH v2 0/4] nvme: protect against possible request reference after completion · Christoph Hellwig <hch@lst.de> · 2021-07-09

From: Christoph Hellwig <hch@lst.de>
Date: 2021-07-09 06:38:05

On Thu, Jul 08, 2021 at 12:02:43PM +0200, Daniel Wagner wrote:

On Thu, Jul 01, 2021 at 01:52:20PM +0200, Christoph Hellwig wrote:

quoted

I think this can go in as soon as we open the nvme-5.15 branch.

nvme-5.15 or nvme-5.14?

5.15.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help