From: Christoph Hellwig <hch@infradead.org>
To: axboe@kernel.dk
Cc: kbusch@kernel.org, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: [GIT PULL] nvme fixes for 5.7
Date: Wed, 8 Apr 2020 08:21:31 +0200 [thread overview]
Message-ID: <20200408062131.GA212017@infradead.org> (raw)
The following changes since commit 458ef2a25e0cbdc216012aa2b9cf549d64133b08:
Merge tag 'x86-timers-2020-03-30' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2020-03-30 19:55:39 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.7
for you to fetch changes up to 21f9024355e58772ec5d7fc3534aa5e29d72a8b6:
nvmet-rdma: fix double free of rdma queue (2020-04-07 18:33:45 +0200)
----------------------------------------------------------------
Israel Rukshin (2):
nvme-rdma: Replace comma with a semicolon
nvmet-rdma: fix double free of rdma queue
James Smart (3):
nvme-fcloop: fix deallocation of working context
nvmet-fc: fix typo in comment
nvme-fc: Revert "add module to ops template to allow module references"
Nick Bowler (1):
nvme: fix compat address handling in several ioctls
Sagi Grimberg (7):
nvme-tcp: fix possible crash in write_zeroes processing
nvme-tcp: don't poll a non-live queue
nvme-tcp: fix possible crash in recv error flow
nvme: inherit stable pages constraint in the mpath stack device
nvmet: fix NULL dereference when removing a referral
nvmet-rdma: fix bonding failover possible NULL deref
nvme: fix deadlock caused by ANA update wrong locking
drivers/nvme/host/core.c | 34 +++++--
drivers/nvme/host/fc.c | 14 +--
drivers/nvme/host/multipath.c | 4 +-
drivers/nvme/host/rdma.c | 2 +-
drivers/nvme/host/tcp.c | 18 ++--
drivers/nvme/target/configfs.c | 10 +-
drivers/nvme/target/fc.c | 2 +-
drivers/nvme/target/fcloop.c | 77 ++++++++++-----
drivers/nvme/target/rdma.c | 205 +++++++++++++++++++++++++++-------------
drivers/scsi/lpfc/lpfc_nvme.c | 2 -
drivers/scsi/qla2xxx/qla_nvme.c | 1 -
include/linux/nvme-fc-driver.h | 4 -
12 files changed, 242 insertions(+), 131 deletions(-)
next reply other threads:[~2020-04-08 6:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 6:21 Christoph Hellwig [this message]
2020-04-08 14:41 ` [GIT PULL] nvme fixes for 5.7 Jens Axboe
2020-05-08 15:39 Christoph Hellwig
2020-05-08 15:49 ` Jens Axboe
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=20200408062131.GA212017@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.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;
as well as URLs for NNTP newsgroup(s).