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>,
Benjamin Marzinski <bmarzins@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: [git pull] device mapper fixes for 6.8-rc3
Date: Fri, 2 Feb 2024 13:00:38 -0500 [thread overview]
Message-ID: <Zb0txmt9K4MMHst3@redhat.com> (raw)
Hi Linus,
The following changes since commit 41bccc98fb7931d63d03f326a746ac4d429c1dd3:
Linux 6.8-rc2 (2024-01-28 17:01:12 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-6.8/dm-fixes
for you to fetch changes up to 0a9bab391e336489169b95cb0d4553d921302189:
dm-crypt, dm-verity: disable tasklets (2024-02-02 12:33:50 -0500)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix DM ioctl interface to avoid INT_MAX overflow warnings from
kvmalloc by limiting the number of targets and parameter size area.
- Fix DM stats to avoid INT_MAX overflow warnings from kvmalloc by
limiting the number of entries supported.
- Fix DM writecache to support mapping devices larger than 1 TiB by
switching from using kvmalloc_array to vmalloc_array -- which avoids
INT_MAX overflow in kvmalloc_node and associated warnings.
- Remove the (ab)use of tasklets from both the DM crypt and verity
targets. They will be converted to use BH workqueue in future.
-----BEGIN PGP SIGNATURE-----
iQEzBAABCAAdFiEEJfWUX4UqZ4x1O2wixSPxCi2dA1oFAmW9LCsACgkQxSPxCi2d
A1qILwgAmL9XOtavSKJ/8o9scJygutYpNSLE0f6mdkdCgJB2nknJ1vR38bXyDpNr
X3s6QC5TqKTtG7DtRTfnZc8zgtBHajjUZTFBu1NUF9kgNQcrjG3jW+quZ51pxkV0
1rvzOiYts6ca8csbFViMPS9FJVq1h3PnAyrkhI0SUS7+jEvDZy/QIX4DP20ye9SX
wKguOSK544haSLHPNYuZqqCEoTBF+Vh1k1gDkxr594NwjsIJJK0+HGelamjzN/96
/jr88P4bm/6OIVdvwTUefnpIhNIum1Dfa8QWciKOzuct0jqsub65+SUSoTLmoiY4
/3AZDvp0ZMEwpMAvCIyvHnm81K72MA==
=sioN
-----END PGP SIGNATURE-----
----------------------------------------------------------------
Mikulas Patocka (4):
dm: limit the number of targets and parameter size area
dm stats: limit the number of entries
dm writecache: allow allocations larger than 2GiB
dm-crypt, dm-verity: disable tasklets
drivers/md/dm-core.h | 2 ++
drivers/md/dm-crypt.c | 38 ++------------------------------------
drivers/md/dm-ioctl.c | 3 ++-
drivers/md/dm-stats.c | 9 +++++++++
drivers/md/dm-table.c | 9 +++++++--
drivers/md/dm-verity-target.c | 26 ++------------------------
drivers/md/dm-verity.h | 1 -
drivers/md/dm-writecache.c | 8 ++++----
8 files changed, 28 insertions(+), 68 deletions(-)
next reply other threads:[~2024-02-02 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 18:00 Mike Snitzer [this message]
2024-02-02 20:43 ` [git pull] device mapper fixes for 6.8-rc3 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=Zb0txmt9K4MMHst3@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.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.