linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	Gabriel Krisman Bertazi <krisman@collabora.com>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Milan Broz <gmazyland@gmail.com>,
	Sunwook Eom <speed.eom@samsung.com>
Subject: [git pull] device mapper fixes for 5.7-rc4
Date: Thu, 30 Apr 2020 18:07:36 -0400	[thread overview]
Message-ID: <20200430220735.GA30584@redhat.com> (raw)

Hi Linus,

The following changes since commit 8267d8fb4819afa76b2a54dca48efdda6f0b1910:

  dm integrity: fix logic bug in integrity tag testing (2020-04-03 13:07:41 -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-2

for you to fetch changes up to 5686dee34dbfe0238c0274e0454fa0174ac0a57a:

  dm multipath: use updated MPATHF_QUEUE_IO on mapping for bio-based mpath (2020-04-28 19:51:46 -0400)

Please pull, thanks!
Mike

----------------------------------------------------------------
- Document DM integrity allow_discard feature that was added during
  5.7 merge window.

- Fix potential for DM writecache data corruption during DM table
  reloads.

- Fix DM verity's FEC support's hash block number calculation in
  verity_fec_decode().

- Fix bio-based DM multipath crash due to use of stale copy of
  MPATHF_QUEUE_IO flag state in __map_bio().

----------------------------------------------------------------
Gabriel Krisman Bertazi (1):
      dm multipath: use updated MPATHF_QUEUE_IO on mapping for bio-based mpath

Mikulas Patocka (1):
      dm writecache: fix data corruption when reloading the target

Milan Broz (1):
      dm integrity: document allow_discard option

Sunwook Eom (1):
      dm verity fec: fix hash block number in verity_fec_decode

 .../admin-guide/device-mapper/dm-integrity.rst     | 15 ++++---
 drivers/md/dm-mpath.c                              |  6 ++-
 drivers/md/dm-verity-fec.c                         |  2 +-
 drivers/md/dm-writecache.c                         | 52 +++++++++++++++-------
 4 files changed, 51 insertions(+), 24 deletions(-)


             reply	other threads:[~2020-04-30 22:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 22:07 Mike Snitzer [this message]
2020-04-30 23:50 ` [git pull] device mapper fixes for 5.7-rc4 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=20200430220735.GA30584@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=gmazyland@gmail.com \
    --cc=krisman@collabora.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=speed.eom@samsung.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;
as well as URLs for NNTP newsgroup(s).