From: Mikulas Patocka <mpatocka@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Heinz Mauelshagen <heinzm@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Milan Broz <gmazyland@gmail.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
dm-devel@lists.linux.dev
Subject: [git pull] device mapper fixes for 6.16
Date: Mon, 23 Jun 2025 18:13:51 +0200 (CEST) [thread overview]
Message-ID: <4ac30b56-92f5-c33c-1270-864fd5ceee90@redhat.com> (raw)
Hi Linus
The following changes since commit 86731a2a651e58953fc949573895f2fa6d456841:
Linux 6.16-rc3 (2025-06-22 13:30:08 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-6.16/dm-fixes
for you to fetch changes up to db53805156f1e0aa6d059c0d3f9ac660d4ef3eb4:
dm-raid: fix variable in journal device check (2025-06-23 16:42:37 +0200)
Please, pull, thanks
Mikulas
----------------------------------------------------------------
- dm-crypt: fix a crash on 32-bit machines
- dm-raid: replace "rdev" with correct loop variable name "r"
-----BEGIN PGP SIGNATURE-----
iIoEABYIADIWIQRnH8MwLyZDhyYfesYTAyx9YGnhbQUCaFl3iRQcbXBhdG9ja2FA
cmVkaGF0LmNvbQAKCRATAyx9YGnhbcRMAP92ueTp0NFJr9dJne79HbhpJkBAS+b+
25/qycKPv2XDfwD/c3/e3sBOhTIK8PohFR7lR62NepdfrOFVaaKubmNUlAU=
=FD8P
-----END PGP SIGNATURE-----
----------------------------------------------------------------
Heinz Mauelshagen (1):
dm-raid: fix variable in journal device check
Herbert Xu (1):
dm-crypt: Extend state buffer size in crypt_iv_lmk_one
drivers/md/dm-crypt.c | 11 +++++++----
drivers/md/dm-raid.c | 2 +-
include/crypto/hash.h | 2 ++
include/crypto/md5.h | 4 ++++
4 files changed, 14 insertions(+), 5 deletions(-)
next reply other threads:[~2025-06-23 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 16:13 Mikulas Patocka [this message]
2025-06-23 22:10 ` [git pull] device mapper fixes for 6.16 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=4ac30b56-92f5-c33c-1270-864fd5ceee90@redhat.com \
--to=mpatocka@redhat.com \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=gmazyland@gmail.com \
--cc=heinzm@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=snitzer@kernel.org \
--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 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 NNTP newsgroup(s).