From: Mike Snitzer <snitzer@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@lists.linux.dev, linux-block@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
Christoph Hellwig <hch@lst.de>,
Fan Wu <wufan@linux.microsoft.com>,
Hongyu Jin <hongyu.jin@unisoc.com>, Lizhe <sensor1010@163.com>,
Ming Lei <ming.lei@redhat.com>
Subject: [git pull] device mapper changes for 6.9
Date: Mon, 11 Mar 2024 14:31:38 -0400 [thread overview]
Message-ID: <Ze9OCmWb-9LX5t8W@redhat.com> (raw)
Hi Linus,
Please note there will be 2 additional DM pull requests that will follow
this one (for BH workqueue changes and the VDO dm target).
The following changes since commit 0e0c50e85a364bb7f1c52c84affe7f9e88c57da7:
dm-crypt, dm-integrity, dm-verity: bump target version (2024-02-20 13:35:47 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-6.9/dm-changes
for you to fetch changes up to 8f28e6d4fe7440fb2c309e71bfcba961f6ad5a18:
dm: call the resume method on internal suspend (2024-03-11 13:58:37 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix DM core's IO submission (which include dm-io and dm-bufio) such
that a bio's IO priority is propagated. Work focused on enabling
both DM crypt and verity targets to retain the appropriate IO
priority.
- Fix DM raid reshape logic to not allow an empty flush bio to be
requeued due to false concern about the bio, which doesn't have a
data payload, accessing beyond the end of the device.
- Fix DM core's internal resume so that it properly calls both presume
and resume methods, which fixes the potential for a postsuspend and
resume imbalance.
- Update DM verity target to set DM_TARGET_SINGLETON flag because it
doesn't make sense to have a DM table with a mix of targets that
include dm-verity.
- Small cleanups in DM crypt, thin, and integrity targets.
- Fix references to dm-devel mailing list to use latest list address.
-----BEGIN PGP SIGNATURE-----
iQEzBAABCAAdFiEEJfWUX4UqZ4x1O2wixSPxCi2dA1oFAmXvSCgACgkQxSPxCi2d
A1oSBAgAvCjWJghtJeUfLQ5crmb1yR3aOETtdTyjPyfoxNoc/BkbixdYc/Ze01fM
exi0UqDY02FYW0OG/ZGF/UU0amayar3narNLkF8a7NqJcsLQaPtHXsqKzkPib8/Z
VWyV69ZAmv63oTn74hNrlehAcRHAx54YxOz8q4rGl1Cg8aMkx5R5IoJDdpgCvDnl
daBPBKT4waMXHScQtBZ7A9+7VIBK16MWzvp3uLIE5GQcoJfjW/K+MQxze57Fb7OE
gu0hBJILkFjiOlT4L4OJecsqOw9poZldJ1miPDAQGUsASRsq3jAR8+61eu/CwxG4
l/vXrZ+Iua9V4ipRLa0gIKFOQLBwOQ==
=sm51
-----END PGP SIGNATURE-----
----------------------------------------------------------------
Christoph Hellwig (2):
dm-integrity: set max_integrity_segments in dm_integrity_io_hints
dm: set the correct discard_sectors limit
Fan Wu (1):
dm verity: set DM_TARGET_SINGLETON feature flag
Hongyu Jin (4):
dm io: Support IO priority
dm bufio: Support IO priority
dm verity: Fix IO priority lost when reading FEC and hash
dm crypt: Fix IO priority lost when queuing write bios
Lizhe (1):
dm crypt: remove redundant state settings after waking up
Mike Snitzer (3):
dm thin: add braces around conditional code that spans lines
dm ioctl: update DM_DRIVER_EMAIL to new dm-devel mailing list
dm: update relevant MODULE_AUTHOR entries to latest dm-devel mailing list
Mikulas Patocka (1):
dm: call the resume method on internal suspend
Ming Lei (1):
dm raid: fix false positive for requeue needed during reshape
drivers/md/dm-bio-prison-v1.c | 2 +-
drivers/md/dm-bufio.c | 76 +++++++++++++++++++--------
drivers/md/dm-cache-policy-smq.c | 2 +-
drivers/md/dm-cache-target.c | 5 +-
drivers/md/dm-clone-target.c | 3 +-
drivers/md/dm-crypt.c | 2 +-
drivers/md/dm-dust.c | 2 +-
drivers/md/dm-ebs-target.c | 2 +-
drivers/md/dm-flakey.c | 2 +-
drivers/md/dm-integrity.c | 14 ++---
drivers/md/dm-io.c | 23 ++++----
drivers/md/dm-ioctl.c | 2 +-
drivers/md/dm-kcopyd.c | 4 +-
drivers/md/dm-log-userspace-base.c | 2 +-
drivers/md/dm-log-writes.c | 2 +-
drivers/md/dm-log.c | 6 +--
drivers/md/dm-mpath.c | 2 +-
drivers/md/dm-ps-round-robin.c | 2 +-
drivers/md/dm-raid.c | 8 +--
drivers/md/dm-raid1.c | 6 +--
drivers/md/dm-region-hash.c | 2 +-
drivers/md/dm-snap-persistent.c | 4 +-
drivers/md/dm-snap.c | 2 +-
drivers/md/dm-thin.c | 27 ++++++----
drivers/md/dm-verity-fec.c | 21 ++++----
drivers/md/dm-verity-target.c | 23 +++++---
drivers/md/dm-writecache.c | 10 ++--
drivers/md/dm.c | 29 +++++++---
drivers/md/persistent-data/dm-block-manager.c | 2 +-
include/linux/dm-bufio.h | 7 +++
include/linux/dm-io.h | 3 +-
31 files changed, 185 insertions(+), 112 deletions(-)
next reply other threads:[~2024-03-11 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 18:31 Mike Snitzer [this message]
2024-03-11 18:37 ` [git pull] device mapper changes to switch to BH workqueue for 6.9 Mike Snitzer
2024-03-13 17:04 ` pr-tracker-bot
2024-03-11 18:43 ` [git pull] device mapper changes to add VDO target " Mike Snitzer
2024-03-13 17:04 ` 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=Ze9OCmWb-9LX5t8W@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=hongyu.jin@unisoc.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mpatocka@redhat.com \
--cc=sensor1010@163.com \
--cc=torvalds@linux-foundation.org \
--cc=wufan@linux.microsoft.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).