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,
	Damien Le Moal <damien.lemoal@wdc.com>
Subject: [git pull] device mapper fixes for 4.20
Date: Wed, 12 Dec 2018 12:56:48 -0500	[thread overview]
Message-ID: <20181212175648.GA25049@redhat.com> (raw)

Hi Linus,

The following changes since commit 2595646791c319cadfdbf271563aac97d0843dc7:

  Linux 4.20-rc5 (2018-12-02 15:07:55 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 2af6c0703d75fc3ff2e6de19b4b3adab96acc12d:

  dm thin: bump target version (2018-12-12 09:39:54 -0500)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fix DM cache metadata to verify that a cache has block before trying
  to continue with operation that requires them.

- Fix bio-based DM core's dm_make_request() to properly impose device
  limits on individual bios by making use of blk_queue_split().

- Fix long-standing race with how DM thinp notified userspace of
  thin-pool mode state changes before they were actually made.

- Fix the zoned target's bio completion handling; this is a fairly
  invassive fix at this stage but it is localized to the zoned target.
  Any zoned target users will benefit from this fix.

----------------------------------------------------------------
Damien Le Moal (1):
      dm zoned: Fix target BIO completion handling

Mike Snitzer (4):
      dm cache metadata: verify cache has blocks in blocks_are_clean_separate_dirty()
      dm: call blk_queue_split() to impose device limits on bios
      dm thin: send event about thin-pool state change _after_ making it
      dm thin: bump target version

 drivers/md/dm-cache-metadata.c |   4 ++
 drivers/md/dm-thin.c           |  72 ++++++++++++------------
 drivers/md/dm-zoned-target.c   | 122 +++++++++++++----------------------------
 drivers/md/dm.c                |   2 +
 4 files changed, 81 insertions(+), 119 deletions(-)

             reply	other threads:[~2018-12-12 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 17:56 Mike Snitzer [this message]
2018-12-13 21:15 ` [git pull] device mapper fixes for 4.20 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=20181212175648.GA25049@redhat.com \
    --to=snitzer@redhat.com \
    --cc=damien.lemoal@wdc.com \
    --cc=dm-devel@redhat.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;
as well as URLs for NNTP newsgroup(s).