From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
Alasdair G Kergon <agk@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: [git pull v2] device mapper fixes for 5.7
Date: Fri, 3 Apr 2020 13:15:43 -0400 [thread overview]
Message-ID: <20200403171543.GA92499@lobo> (raw)
In-Reply-To: <20200403154213.GA18386@redhat.com>
Hi Linus,
I updated the tag after my initial pull request to include one more
fix from Mikulas.
The following changes since commit 81d5553d1288c2ec0390f02f84d71ca0f0f9f137:
dm clone metadata: Fix return type of dm_clone_nr_of_hydrated_regions() (2020-03-27 14:42:51 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.7/dm-fixes
for you to fetch changes up to 8267d8fb4819afa76b2a54dca48efdda6f0b1910:
dm integrity: fix logic bug in integrity tag testing (2020-04-03 13:07:41 -0400)
Please pull, thanks!
Mike
----------------------------------------------------------------
- Fix excessive bio splitting that caused performance regressions.
- Fix logic bug in DM integrity discard support's integrity tag
testing.
- Fix DM integrity warning on ppc64le due to missing cast.
----------------------------------------------------------------
Mike Snitzer (2):
dm integrity: fix ppc64le warning
Revert "dm: always call blk_queue_split() in dm_process_bio()"
Mikulas Patocka (1):
dm integrity: fix logic bug in integrity tag testing
drivers/md/dm-integrity.c | 4 ++--
drivers/md/dm.c | 5 +++--
2 files changed, 5 insertions(+), 4 deletions(-)
next prev parent reply other threads:[~2020-04-03 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 15:42 [git pull] device mapper fixes for 5.7 Mike Snitzer
2020-04-03 17:15 ` Mike Snitzer [this message]
2020-04-03 22:05 ` [git pull v2] " pr-tracker-bot
2020-04-03 22:05 ` [git pull] " 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=20200403171543.GA92499@lobo \
--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 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.