From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 5.3-rc5
Date: Sat, 17 Aug 2019 16:45:14 -0600 [thread overview]
Message-ID: <cb805bba-1f68-15bc-a8eb-ebbce15e1dfa@kernel.dk> (raw)
Hi Linus,
Collection of fixes that should go into this series. This pull request
contains:
- Revert of the REQ_NOWAIT_INLINE and associated dio changes. There were
still corner cases there, and even though I had a solution for it,
it's too involved for this stage. (me)
- Set of NVMe fixes (via Sagi)
- io_uring fix for fixed buffers (Anthony)
- io_uring defer issue fix (Jackie)
- Regression fix for queue sync at exit time (zhengbin)
- xen blk-back memory leak fix (Wenwen)
Please pull!
git://git.kernel.dk/linux-block.git tags/for-linus-2019-08-17
----------------------------------------------------------------
Aleix Roca Nonell (1):
io_uring: fix manual setup of iov_iter for fixed buffers
Anthony Iliopoulos (1):
nvme-multipath: revalidate nvme_ns_head gendisk in nvme_validate_ns
Jackie Liu (1):
io_uring: fix an issue when IOSQE_IO_LINK is inserted into defer list
Jens Axboe (2):
Merge branch 'nvme-5.3-rc' of git://git.infradead.org/nvme into for-linus
block: remove REQ_NOWAIT_INLINE
Keith Busch (1):
nvme-pci: Fix async probe remove race
Logan Gunthorpe (4):
nvmet: Fix use-after-free bug when a port is removed
nvmet-loop: Flush nvme_delete_wq when removing the port
nvmet-file: fix nvmet_file_flush() always returning an error
nvme-core: Fix extra device_put() call on error path
Sagi Grimberg (3):
nvme: fix a possible deadlock when passthru commands sent to a multipath device
nvme-rdma: fix possible use-after-free in connect error flow
nvme: fix controller removal race with scan work
Wenwen Wang (1):
xen/blkback: fix memory leaks
zhengbin (1):
blk-mq: move cancel of requeue_work to the front of blk_exit_queue
block/blk-mq.c | 10 +----
block/blk-sysfs.c | 3 ++
drivers/block/xen-blkback/xenbus.c | 6 +--
drivers/nvme/host/core.c | 15 +++++++-
drivers/nvme/host/multipath.c | 76 +++++++++++++++++++++++++++++++++++---
drivers/nvme/host/nvme.h | 21 ++++++++++-
drivers/nvme/host/pci.c | 3 +-
drivers/nvme/host/rdma.c | 16 +++++---
drivers/nvme/target/configfs.c | 1 +
drivers/nvme/target/core.c | 15 ++++++++
drivers/nvme/target/loop.c | 8 ++++
drivers/nvme/target/nvmet.h | 3 ++
fs/block_dev.c | 49 +++---------------------
fs/io_uring.c | 20 +++++-----
include/linux/blk_types.h | 5 +--
15 files changed, 167 insertions(+), 84 deletions(-)
--
Jens Axboe
next reply other threads:[~2019-08-17 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 22:45 Jens Axboe [this message]
2019-08-18 2:50 ` [GIT PULL] Block fixes for 5.3-rc5 pr-tracker-bot
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=cb805bba-1f68-15bc-a8eb-ebbce15e1dfa@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@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 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).