All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@kernel.org>,
	 dm-devel@lists.linux.dev
Subject: [git pull] device mapper fixes for 6.17
Date: Wed, 17 Sep 2025 16:16:18 +0200 (CEST)	[thread overview]
Message-ID: <26358e47-e03b-82f0-5bf6-2cc2db3ec8ef@redhat.com> (raw)

Hi Linus

The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:

  Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-6.17/dm-fixes

for you to fetch changes up to a86556264696b797d94238d99d8284d0d34ed960:

  dm-raid: don't set io_min and io_opt for raid1 (2025-09-17 16:04:29 +0200)

Please, pull, thanks
Mikulas

----------------------------------------------------------------
- fix integer overflow in dm-stripe

- limit tag size in dm-integrity to 255 bytes

- fix 'alignment inconsistency' warning in dm-raid
-----BEGIN PGP SIGNATURE-----

iIoEABYIADIWIQRnH8MwLyZDhyYfesYTAyx9YGnhbQUCaMrAdRQcbXBhdG9ja2FA
cmVkaGF0LmNvbQAKCRATAyx9YGnhbYhtAQDsWJHG7dOVuvoY+kyM9SmC2My6l5u2
awYBsjVT//9KDAD/c6s+ffeseY6VpBuFmPx5i75ieCmUcuKTMUxgdIErPwM=
=FXwZ
-----END PGP SIGNATURE-----

----------------------------------------------------------------
Mikulas Patocka (3):
      dm-stripe: fix a possible integer overflow
      dm-integrity: limit MAX_TAG_SIZE to 255
      dm-raid: don't set io_min and io_opt for raid1

 drivers/md/dm-integrity.c |  2 +-
 drivers/md/dm-raid.c      |  6 ++++--
 drivers/md/dm-stripe.c    | 10 +++++++---
 3 files changed, 12 insertions(+), 6 deletions(-)


             reply	other threads:[~2025-09-17 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 14:16 Mikulas Patocka [this message]
2025-09-17 18:38 ` [git pull] device mapper fixes for 6.17 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=26358e47-e03b-82f0-5bf6-2cc2db3ec8ef@redhat.com \
    --to=mpatocka@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --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 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.