From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Diego Calleja <diegocg@gmail.com>,
Nikos Tsironis <ntsironis@arrikto.com>,
Eric Biggers <ebiggers@google.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Hou Tao <houtao1@huawei.com>, Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fixes for 5.5-rc2
Date: Thu, 12 Dec 2019 09:58:57 -0500 [thread overview]
Message-ID: <20191212145857.GA27301@redhat.com> (raw)
Hi Linus,
The following changes since commit f612b2132db529feac4f965f28a1b9258ea7c22b:
Revert "dm crypt: use WQ_HIGHPRI for the IO and crypt workqueues" (2019-11-20 17:27:39 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.5/dm-fixes
for you to fetch changes up to 7fc979f8204fb763e203d3e716c17d352eb96b35:
docs: dm-integrity: remove reference to ARC4 (2019-12-10 10:02:43 -0500)
Please pull, thanks!
Mike
----------------------------------------------------------------
- Fix DM multipath by restoring full path selector functionality for
bio-based configurations that don't haave a SCSI device handler.
- Fix dm-btree removal to ensure non-root btree nodes have at least
(max_entries / 3) entries. This resolves userspace thin_check
utility's report of "too few entries in btree_node".
- Fix both the DM thin-provisioning and dm-clone targets to properly
flush the data device prior to metadata commit. This resolves the
potential for inconsistency across a power loss event when the data
device has a volatile writeback cache.
- Small documentation fixes to dm-clone and dm-integrity.
----------------------------------------------------------------
Diego Calleja (1):
dm: add dm-clone to the documentation index
Eric Biggers (1):
docs: dm-integrity: remove reference to ARC4
Hou Tao (1):
dm btree: increase rebalance threshold in __rebalance2()
Mike Snitzer (1):
dm mpath: remove harmful bio-based optimization
Nikos Tsironis (5):
dm clone metadata: Track exact changes per transaction
dm clone metadata: Use a two phase commit
dm clone: Flush destination device before committing metadata
dm thin metadata: Add support for a pre-commit callback
dm thin: Flush data device before committing metadata
.../admin-guide/device-mapper/dm-integrity.rst | 2 +-
Documentation/admin-guide/device-mapper/index.rst | 1 +
drivers/md/dm-clone-metadata.c | 136 +++++++++++++++------
drivers/md/dm-clone-metadata.h | 17 +++
drivers/md/dm-clone-target.c | 53 ++++++--
drivers/md/dm-mpath.c | 37 +-----
drivers/md/dm-thin-metadata.c | 29 +++++
drivers/md/dm-thin-metadata.h | 7 ++
drivers/md/dm-thin.c | 42 ++++++-
drivers/md/persistent-data/dm-btree-remove.c | 8 +-
10 files changed, 248 insertions(+), 84 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-block@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>,
Diego Calleja <diegocg@gmail.com>,
Eric Biggers <ebiggers@google.com>, Hou Tao <houtao1@huawei.com>,
Nikos Tsironis <ntsironis@arrikto.com>
Subject: [git pull] device mapper fixes for 5.5-rc2
Date: Thu, 12 Dec 2019 09:58:57 -0500 [thread overview]
Message-ID: <20191212145857.GA27301@redhat.com> (raw)
Hi Linus,
The following changes since commit f612b2132db529feac4f965f28a1b9258ea7c22b:
Revert "dm crypt: use WQ_HIGHPRI for the IO and crypt workqueues" (2019-11-20 17:27:39 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.5/dm-fixes
for you to fetch changes up to 7fc979f8204fb763e203d3e716c17d352eb96b35:
docs: dm-integrity: remove reference to ARC4 (2019-12-10 10:02:43 -0500)
Please pull, thanks!
Mike
----------------------------------------------------------------
- Fix DM multipath by restoring full path selector functionality for
bio-based configurations that don't haave a SCSI device handler.
- Fix dm-btree removal to ensure non-root btree nodes have at least
(max_entries / 3) entries. This resolves userspace thin_check
utility's report of "too few entries in btree_node".
- Fix both the DM thin-provisioning and dm-clone targets to properly
flush the data device prior to metadata commit. This resolves the
potential for inconsistency across a power loss event when the data
device has a volatile writeback cache.
- Small documentation fixes to dm-clone and dm-integrity.
----------------------------------------------------------------
Diego Calleja (1):
dm: add dm-clone to the documentation index
Eric Biggers (1):
docs: dm-integrity: remove reference to ARC4
Hou Tao (1):
dm btree: increase rebalance threshold in __rebalance2()
Mike Snitzer (1):
dm mpath: remove harmful bio-based optimization
Nikos Tsironis (5):
dm clone metadata: Track exact changes per transaction
dm clone metadata: Use a two phase commit
dm clone: Flush destination device before committing metadata
dm thin metadata: Add support for a pre-commit callback
dm thin: Flush data device before committing metadata
.../admin-guide/device-mapper/dm-integrity.rst | 2 +-
Documentation/admin-guide/device-mapper/index.rst | 1 +
drivers/md/dm-clone-metadata.c | 136 +++++++++++++++------
drivers/md/dm-clone-metadata.h | 17 +++
drivers/md/dm-clone-target.c | 53 ++++++--
drivers/md/dm-mpath.c | 37 +-----
drivers/md/dm-thin-metadata.c | 29 +++++
drivers/md/dm-thin-metadata.h | 7 ++
drivers/md/dm-thin.c | 42 ++++++-
drivers/md/persistent-data/dm-btree-remove.c | 8 +-
10 files changed, 248 insertions(+), 84 deletions(-)
next reply other threads:[~2019-12-12 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 14:58 Mike Snitzer [this message]
2019-12-12 14:58 ` [git pull] device mapper fixes for 5.5-rc2 Mike Snitzer
2019-12-13 23:10 ` pr-tracker-bot
2019-12-13 23:10 ` 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=20191212145857.GA27301@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=diegocg@gmail.com \
--cc=dm-devel@redhat.com \
--cc=ebiggers@google.com \
--cc=houtao1@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=ntsironis@arrikto.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.