From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bart Van Assche <bart.vanassche@wdc.com>,
dm-devel@redhat.com, Kees Cook <keescook@chromium.org>,
Arnd Bergmann <arnd@arndb.de>,
Ross Zwisler <ross.zwisler@linux.intel.com>
Subject: [git pull] device mapper fixes for 4.18-rc3
Date: Thu, 28 Jun 2018 17:34:16 -0400 [thread overview]
Message-ID: <20180628213416.GA20090@redhat.com> (raw)
Hi Linus,
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-4.18/dm-fixes
for you to fetch changes up to dbc626597c39b24cefce09fbd8e9dea85869a801:
dm: prevent DAX mounts if not supported (2018-06-28 16:06:14 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix dm core to use more efficient bio_split() instead of
bio_clone_bioset(). Also fixes splitting bio that has integrity
payload.
- Three fixes related to properly validating DAX capabilities of a
stacked DM device that will advertise DAX support.
- Update DM writecache target to use 2-factor allocator arguments. Kees
says this is the last related change for 4.18.
- Fix DM zoned target to use GFP_NOIO to avoid triggering reclaim during
IO submission (caught by lockdep).
- Fix DM thinp to gracefully recover from running out of data space
while a previous async discard completes (whereby freeing space).
- Fix DM thinp's metadata transaction commit to avoid needless work.
----------------------------------------------------------------
Arnd Bergmann (1):
dm raid: don't use 'const' in function return
Bart Van Assche (1):
dm zoned: avoid triggering reclaim from inside dmz_map()
Kees Cook (1):
dm writecache: use 2-factor allocator arguments
Mike Snitzer (3):
dm: use bio_split() when splitting out the already processed bio
dm thin metadata: remove needless work from __commit_transaction
dm thin: handle running out of data space vs concurrent discard
Ross Zwisler (3):
pmem: only set QUEUE_FLAG_DAX for fsdax mode
dax: check for QUEUE_FLAG_DAX in bdev_dax_supported()
dm: prevent DAX mounts if not supported
drivers/dax/super.c | 8 ++++++++
drivers/md/dm-raid.c | 2 +-
drivers/md/dm-table.c | 7 ++++---
drivers/md/dm-thin-metadata.c | 9 ---------
drivers/md/dm-thin.c | 11 +++++++++--
drivers/md/dm-writecache.c | 10 +++++-----
drivers/md/dm-zoned-target.c | 2 +-
drivers/md/dm.c | 8 +++-----
drivers/nvdimm/pmem.c | 3 ++-
9 files changed, 33 insertions(+), 27 deletions(-)
reply other threads:[~2018-06-28 21:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180628213416.GA20090@redhat.com \
--to=snitzer@redhat.com \
--cc=arnd@arndb.de \
--cc=bart.vanassche@wdc.com \
--cc=dm-devel@redhat.com \
--cc=keescook@chromium.org \
--cc=ross.zwisler@linux.intel.com \
--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.