Linux block layer
 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>, Joe Thornber <ejt@redhat.com>,
	Milan Broz <gmazyland@gmail.com>
Subject: [git pull] device mapper fixes for 5.0-rc4
Date: Thu, 24 Jan 2019 14:38:29 -0500	[thread overview]
Message-ID: <20190124193829.GA22312@redhat.com> (raw)

Hi Linus,

The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:

  Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 075c18c3e124a1511ebc10a89f1858c8a77dcb01:

  dm: add missing trace_block_split() to __split_and_process_bio() (2019-01-22 13:41:48 -0500)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fix DM crypt's parsing of extended IV arguments.

- Fix DM thinp's discard passdown to properly account for extra
  reference that is taken to guard against reallocating a block before a
  discard has been issued.

- Fix bio-based DM's redundant IO accounting that was occurring for bios
  that must be split due to the nature of the DM target (e.g. dm-stripe,
  dm-thinp, etc).

----------------------------------------------------------------
Joe Thornber (1):
      dm thin: fix passdown_double_checking_shared_status()

Mike Snitzer (4):
      dm: fix clone_bio() to trigger blk_recount_segments()
      dm: fix redundant IO accounting for bios that need splitting
      dm: fix dm_wq_work() to only use __split_and_process_bio() if appropriate
      dm: add missing trace_block_split() to __split_and_process_bio()

Milan Broz (1):
      dm crypt: fix parsing of extended IV arguments

 drivers/md/dm-crypt.c         | 25 +++++++++++++++++--------
 drivers/md/dm-thin-metadata.c |  4 ++--
 drivers/md/dm-thin-metadata.h |  2 +-
 drivers/md/dm-thin.c          | 10 +++++-----
 drivers/md/dm.c               | 43 +++++++++++++++++++++++++++++++------------
 5 files changed, 56 insertions(+), 28 deletions(-)

             reply	other threads:[~2019-01-24 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-24 19:38 Mike Snitzer [this message]
2019-01-24 20:15 ` [git pull] device mapper fixes for 5.0-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=20190124193829.GA22312@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --cc=gmazyland@gmail.com \
    --cc=linux-block@vger.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