From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-block@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: [git pull] device mapper fixes for 5.13-rc3
Date: Thu, 20 May 2021 15:45:46 -0400 [thread overview]
Message-ID: <YKa8aq2SgXzX7sva@redhat.com> (raw)
Hi Linus,
The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:
Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.13/dm-fixes
for you to fetch changes up to bc8f3d4647a99468d7733039b6bc9234b6e91df4:
dm integrity: fix sparse warnings (2021-05-13 14:53:49 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- Fix a couple DM snapshot target crashes exposed by user-error.
- Fix DM integrity target to not use discard optimization, introduced
during 5.13 merge, when recalulating.
- Fix some sparse warnings in DM integrity target.
----------------------------------------------------------------
Mikulas Patocka (4):
dm snapshot: fix a crash when an origin has no snapshots
dm snapshot: fix crash with transient storage and zero chunk size
dm integrity: revert to not using discard filler when recalulating
dm integrity: fix sparse warnings
drivers/md/dm-integrity.c | 81 +++++++++++++++++++++--------------------------
drivers/md/dm-snap.c | 6 ++--
2 files changed, 39 insertions(+), 48 deletions(-)
next reply other threads:[~2021-05-20 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 19:45 Mike Snitzer [this message]
2021-05-21 0:48 ` [git pull] device mapper fixes for 5.13-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=YKa8aq2SgXzX7sva@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox