From: Daniel Wagner <dwagner@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2 0/4] nvme: protect against possible request reference after completion
Date: Thu, 8 Jul 2021 12:02:43 +0200 [thread overview]
Message-ID: <20210708100243.ibmntolineesakyj@beryllium.lan> (raw)
In-Reply-To: <20210701115220.GA12095@lst.de>
On Thu, Jul 01, 2021 at 01:52:20PM +0200, Christoph Hellwig wrote:
> I think this can go in as soon as we open the nvme-5.15 branch.
nvme-5.15 or nvme-5.14?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-07-08 10:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 17:43 [PATCH v2 0/4] nvme: protect against possible request reference after completion Sagi Grimberg
2021-05-19 17:43 ` [PATCH v2 1/4] params: lift param_set_uint_minmax to common code Sagi Grimberg
2021-05-19 21:10 ` Chaitanya Kulkarni
2021-05-20 6:01 ` Christoph Hellwig
2021-05-19 17:43 ` [PATCH v2 2/4] nvme-pci: limit maximum queue depth to 4095 Sagi Grimberg
2021-05-19 21:12 ` Chaitanya Kulkarni
2021-05-26 8:55 ` Hannes Reinecke
2021-05-19 17:43 ` [PATCH v2 3/4] nvme-tcp: don't check blk_mq_tag_to_rq when receiving pdu data Sagi Grimberg
2021-05-26 8:56 ` Hannes Reinecke
2021-05-19 17:43 ` [PATCH v2 4/4] nvme: code command_id with a genctr for use-after-free validation Sagi Grimberg
2021-05-20 6:49 ` Daniel Wagner
2021-05-25 22:50 ` Max Gurtovoy
2021-05-26 0:39 ` Keith Busch
2021-05-26 1:47 ` Chaitanya Kulkarni
2021-05-26 8:41 ` Sagi Grimberg
2021-05-26 8:48 ` Hannes Reinecke
2021-05-26 9:26 ` Max Gurtovoy
2021-05-26 8:59 ` Hannes Reinecke
2021-06-16 16:28 ` [PATCH v2 0/4] nvme: protect against possible request reference after completion Sagi Grimberg
2021-06-16 17:04 ` Keith Busch
2021-06-16 21:05 ` Sagi Grimberg
2021-07-01 11:51 ` Daniel Wagner
2021-07-01 11:52 ` Christoph Hellwig
2021-07-08 10:02 ` Daniel Wagner [this message]
2021-07-09 6:37 ` Christoph Hellwig
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=20210708100243.ibmntolineesakyj@beryllium.lan \
--to=dwagner@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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.