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.7-rc5
Date: Fri, 8 May 2020 21:16:58 -0600 [thread overview]
Message-ID: <cc854168-7859-49f9-63f7-dbaaff8fbb3d@kernel.dk> (raw)
Hi Linus,
A few fixes that should go into this series:
- Small series fixing a use-after-free of bdi name (Christoph,Yufen)
- NVMe pull request, fixing a regression with the smaller CQ update and
a hang at namespace scanning error recovery
- Fix race with blk-iocost iocg->abs_vdebt updates (Tejun)
Please pull!
git://git.kernel.dk/linux-block.git tags/block-5.7-2020-05-08
----------------------------------------------------------------
Alexey Dobriyan (1):
nvme-pci: fix "slimmer CQ head update"
Christoph Hellwig (3):
vboxsf: don't use the source name in the bdi name
bdi: move bdi_dev_name out of line
bdi: add a ->dev_name field to struct backing_dev_info
Jens Axboe (1):
Merge branch 'nvme-5.7' of git://git.infradead.org/nvme into block-5.7
Sagi Grimberg (1):
nvme: fix possible hang when ns scanning fails during error recovery
Tejun Heo (1):
iocost: protect iocg->abs_vdebt with iocg->waitq.lock
Yufen Yu (1):
bdi: use bdi_dev_name() to get device name
block/bfq-iosched.c | 5 +-
block/blk-cgroup.c | 2 +-
block/blk-iocost.c | 117 ++++++++++++++++++++++++---------------
drivers/nvme/host/core.c | 2 +-
drivers/nvme/host/pci.c | 6 +-
fs/ceph/debugfs.c | 2 +-
fs/vboxsf/super.c | 2 +-
include/linux/backing-dev-defs.h | 1 +
include/linux/backing-dev.h | 9 +--
include/trace/events/wbt.h | 8 +--
mm/backing-dev.c | 13 ++++-
tools/cgroup/iocost_monitor.py | 7 ++-
12 files changed, 106 insertions(+), 68 deletions(-)
--
Jens Axboe
next reply other threads:[~2020-05-09 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 3:16 Jens Axboe [this message]
2020-05-09 19:40 ` [GIT PULL] Block fixes for 5.7-rc5 Linus Torvalds
2020-05-09 21: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=cc854168-7859-49f9-63f7-dbaaff8fbb3d@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 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.