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>, Theodore Ts'o <tytso@mit.edu>
Subject: [git pull] device mapper fixes for 6.10-rc1
Date: Tue, 21 May 2024 11:51:30 -0400 [thread overview]
Message-ID: <ZkzDAsx_7FvmFbSX@kernel.org> (raw)
Hi Linus,
The following changes since commit 8b21ac87d550acc4f6207764fed0cf6f0e3966cd:
dm-delay: remove timer_lock (2024-05-09 09:10:58 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-6.10/dm-fixes
for you to fetch changes up to 825d8bbd2f32cb229c3b6653bd454832c3c20acb:
dm: always manage discard support in terms of max_hw_discard_sectors (2024-05-20 15:51:19 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix DM discard regressions due to DM core switching over to using
queue_limits_set() without DM core and targets first being updated
to set (and stack) discard limits in terms of max_hw_discard_sectors
and not max_discard_sectors.
- Fix stable@ DM integrity discard support to set device's
discard_granularity limit to the device's logical block size.
-----BEGIN PGP SIGNATURE-----
iQEzBAABCAAdFiEEJfWUX4UqZ4x1O2wixSPxCi2dA1oFAmZMv3kACgkQxSPxCi2d
A1pX2gf+NjaTP+6otMJ44sYwUGHuWtgwDy7NcoTiF4RvLQjjrUh8Lgm2p3i4evFs
4AzMNXy5V6/mEx/AZb7sjCtPkIGOykkBud3+jhStohQKvXEJQcYtwACNv151NW2c
Fw2tcPZbPKH8P8UkDkegLaCu+4DotYjhuw44dfHFVZ95Wlhcm2UmcjWQEf/LtYW0
Si2FE0z2n1yi1mY6cExuL0bJ+LaMrXRQzHE3ZPaPRn4PFNUTY1juKsHYbgyL7cZ+
xQM1W/KBrKzDztCJGKH4Cl86L3kNPRkiQ7BQ/2Wtse20o10EGT0+lPvevCNcPNpi
gbjAo7OPy9WPA9N/AR8Wfj06YQFaGA==
=Pp+x
-----END PGP SIGNATURE-----
----------------------------------------------------------------
Mike Snitzer (1):
dm: always manage discard support in terms of max_hw_discard_sectors
Mikulas Patocka (1):
dm-integrity: set discard_granularity to logical block size
drivers/md/dm-cache-target.c | 5 ++---
drivers/md/dm-clone-target.c | 4 ++--
drivers/md/dm-integrity.c | 1 +
drivers/md/dm-log-writes.c | 2 +-
drivers/md/dm-snap.c | 2 +-
drivers/md/dm-target.c | 1 -
drivers/md/dm-thin.c | 4 ++--
drivers/md/dm-zero.c | 1 -
drivers/md/dm-zoned-target.c | 1 -
drivers/md/dm.c | 2 +-
10 files changed, 10 insertions(+), 13 deletions(-)
next reply other threads:[~2024-05-21 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 15:51 Mike Snitzer [this message]
2024-05-21 18:53 ` [git pull] device mapper fixes for 6.10-rc1 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=ZkzDAsx_7FvmFbSX@kernel.org \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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.