From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 4.9-rc
Date: Thu, 17 Nov 2016 14:36:12 -0700 [thread overview]
Message-ID: <f072dd2e-8a79-e768-1525-470cbd4e9da4@kernel.dk> (raw)
Hi Linus,
A set of fixes, one for NVMe from Keith, and a set for nvme-{rdma,t,f}
from the usual suspects, fixing actual problems that would be a shame to
release 4.9 with.
Please pull!
git://git.kernel.dk/linux-block.git for-linus
----------------------------------------------------------------
Bart Van Assche (1):
nvmet-rdma: Fix possible NULL deref when handling rdma cm events
Christoph Hellwig (1):
nvme-rdma: reject non-connect commands before the queue is live
Jens Axboe (1):
Merge branch 'nvmf-4.9-rc' of
git://git.infradead.org/nvme-fabrics into for-linus
Keith Busch (1):
nvme/pci: Don't free queues on error
Sagi Grimberg (3):
nvmet: Don't queue fatal error work if csts.cfs is set
nvmet-rdma: don't forget to delete a queue from the list of
connection failed
nvmet-rdma: drain the queue-pair just before freeing it
Steve Wise (1):
nvme-rdma: stop and free io queues on connect failure
drivers/nvme/host/pci.c | 18 ++++--------------
drivers/nvme/host/rdma.c | 42 +++++++++++++++++++++++++++++++++++++++---
drivers/nvme/target/core.c | 10 +++++++---
drivers/nvme/target/rdma.c | 18 +++++++++++++++---
4 files changed, 65 insertions(+), 23 deletions(-)
--
Jens Axboe
next reply other threads:[~2016-11-17 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 21:36 Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-12 0:11 [GIT PULL] Block fixes for 4.9-rc Jens Axboe
2016-11-12 0:45 ` Linus Torvalds
2016-11-12 0:45 ` Linus Torvalds
2016-11-12 1:24 ` Jens Axboe
2016-10-27 16:39 Jens Axboe
2016-10-21 16:09 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=f072dd2e-8a79-e768-1525-470cbd4e9da4@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.