From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: sagi@grimberg.me, linux-nvme@lists.infradead.org, hch@lst.de
Subject: [GIT PULL] nvme fixes for 5.4
Date: Fri, 18 Oct 2019 23:37:00 +0900 [thread overview]
Message-ID: <20191018143700.GB7124@redsun51.ssa.fujisawa.hgst.com> (raw)
Hi Jens,
This is a collection of bug fixes committed since the previous pull
request that address deadlocks, double resets, memory leaks, and other
regression.
The following changes since commit a9eb49c964884654dd6394cb6abe7ceb021c9c96:
block: sed-opal: fix sparse warning: convert __be64 data (2019-10-03 14:21:32 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.4
for you to fetch changes up to a4f40484e7f1dff56bb9f286cc59ffa36e0259eb:
nvme-pci: Set the prp2 correctly when using more than 4k page (2019-10-18 23:09:41 +0900)
----------------------------------------------------------------
Ard Biesheuvel (1):
nvme: retain split access workaround for capability reads
Keith Busch (5):
nvme-pci: Free tagset if no IO queues
nvme: Remove ADMIN_ONLY state
nvme: Restart request timers in resetting state
nvme: Prevent resets during paused controller state
nvme: Wait for reset state when required
Kevin Hao (1):
nvme-pci: Set the prp2 correctly when using more than 4k page
Max Gurtovoy (2):
nvmet-loop: fix possible leakage during error flow
nvme-tcp: fix possible leakage during error flow
Sagi Grimberg (1):
nvme: fix possible deadlock when nvme_update_formats fails
Sebastian Andrzej Siewior (1):
nvme-tcp: Initialize sk->sk_ll_usec only with NET_RX_BUSY_POLL
drivers/nvme/host/core.c | 94 ++++++++++++++++++++++++++++++++-------------
drivers/nvme/host/fabrics.h | 3 +-
drivers/nvme/host/nvme.h | 5 ++-
drivers/nvme/host/pci.c | 83 +++++++++++++++++++++++----------------
drivers/nvme/host/rdma.c | 8 ++++
drivers/nvme/host/tcp.c | 11 ++++++
drivers/nvme/target/loop.c | 4 +-
7 files changed, 144 insertions(+), 64 deletions(-)
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2019-10-18 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 14:37 Keith Busch [this message]
2019-10-18 14:50 ` [GIT PULL] nvme fixes for 5.4 Jens Axboe
2019-10-29 14:35 Keith Busch
2019-10-29 14:55 ` 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=20191018143700.GB7124@redsun51.ssa.fujisawa.hgst.com \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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).