Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Leng <lengchao@huawei.com>
To: <linux-nvme@lists.infradead.org>
Cc: kbusch@kernel.org, axboe@fb.com, hch@lst.de, lengchao@huawei.com,
	sagi@grimberg.me
Subject: [PATCH v2 0/2] avoid request double completion for concurrent nvme_rdma(tcp)_timeout
Date: Thu, 14 Jan 2021 17:09:24 +0800	[thread overview]
Message-ID: <20210114090926.12109-1-lengchao@huawei.com> (raw)

Concurrent nvme_rdma(tcp)_timeout may cause: complete request
before the qp is fully drained(the io work is completely canceled) may
lead to a use-after-free condition.
The patch sets fix it.

Chao Leng (2):
  nvme-rdma: avoid request double completion for concurrent
    nvme_rdma_timeout
  nvme-tcp: avoid request double completion for concurrent
    nvme_tcp_timeout

 drivers/nvme/host/rdma.c | 15 +++++++++++----
 drivers/nvme/host/tcp.c  | 14 ++++++++++----
 2 files changed, 21 insertions(+), 8 deletions(-)

-- 
2.16.4


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

             reply	other threads:[~2021-01-14  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  9:09 Chao Leng [this message]
2021-01-14  9:09 ` [PATCH v2 1/2] nvme-rdma: avoid request double completion for concurrent nvme_rdma_timeout Chao Leng
2021-01-14 16:34   ` Israel Rukshin
2021-01-14  9:09 ` [PATCH v2 2/2] nvme-tcp: avoid request double completion for concurrent nvme_tcp_timeout Chao Leng
2021-01-18 17:59 ` [PATCH v2 0/2] avoid request double completion for concurrent nvme_rdma(tcp)_timeout 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=20210114090926.12109-1-lengchao@huawei.com \
    --to=lengchao@huawei.com \
    --cc=axboe@fb.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox