From: Sagi Grimberg <sagi@grimberg.me>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>
Subject: [GIT PULL] nvme fixes for 5.9 next rc
Date: Sat, 29 Aug 2020 08:32:43 -0700 [thread overview]
Message-ID: <20200829153243.324252-1-sagi@grimberg.me> (raw)
Hey Jens,
Some more nvme fixes:
- instance leak and io boundary fixes from Keith
- fc locking fix from Christophe
- various tcp/rdma reset during traffic fixes from Me
- pci use-after-free fix from Tong
- tcp target null deref fix from Ziye
Please pull.
The following changes since commit a433d7217feab712ff69ef5cc2a86f95ed1aca40:
Merge branch 'md-fixes' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md into block-5.9 (2020-08-28 07:52:02 -0600)
are available in the Git repository at:
ssh://git.infradead.org/var/lib/git/nvme.git nvme-5.9-rc
for you to fetch changes up to 7ad92f656bddff4cf8f641e0e3b1acd4eb9644cb:
nvme-pci: cancel nvme device request before disabling (2020-08-28 16:43:57 -0700)
----------------------------------------------------------------
Christophe JAILLET (1):
nvmet-fc: Fix a missed _irqsave version of spin_lock in 'nvmet_fc_fod_op_done()'
Keith Busch (2):
nvme: fix controller instance leak
nvme: only use power of two io boundaries
Sagi Grimberg (9):
nvme-fabrics: don't check state NVME_CTRL_NEW for request acceptance
nvme: have nvme_wait_freeze_timeout return if it timed out
nvme-tcp: serialize controller teardown sequences
nvme-tcp: fix timeout handler
nvme-tcp: fix reset hang if controller died in the middle of a reset
nvme-rdma: serialize controller teardown sequences
nvme-rdma: fix timeout handler
nvme-rdma: fix reset hang if controller died in the middle of a reset
nvme: Fix NULL dereference for pci nvme controllers
Tong Zhang (1):
nvme-pci: cancel nvme device request before disabling
Ziye Yang (1):
nvmet-tcp: Fix NULL dereference when a connect data comes in h2cdata pdu
drivers/nvme/host/core.c | 56 ++++++++++++++++++++++++-------
drivers/nvme/host/fabrics.c | 1 -
drivers/nvme/host/nvme.h | 2 +-
drivers/nvme/host/pci.c | 4 +--
drivers/nvme/host/rdma.c | 68 ++++++++++++++++++++++++++++----------
drivers/nvme/host/tcp.c | 80 ++++++++++++++++++++++++++++++++-------------
drivers/nvme/target/fc.c | 4 +--
drivers/nvme/target/tcp.c | 10 +++++-
8 files changed, 167 insertions(+), 58 deletions(-)
next reply other threads:[~2020-08-29 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 15:32 Sagi Grimberg [this message]
2020-08-29 16:55 ` [GIT PULL] nvme fixes for 5.9 next rc Jens Axboe
2020-08-30 10:23 ` Sagi Grimberg
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=20200829153243.324252-1-sagi@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).