Linux Device Mapper development
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Heinz Mauelshagen <heinzm@redhat.com>,
	dm-devel@redhat.com, Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fixes for 4.11-rc1
Date: Thu, 2 Mar 2017 10:39:17 -0500	[thread overview]
Message-ID: <20170302153916.GA35026@redhat.com> (raw)

Hi Linus,

The following changes since commit d67a5f4b5947aba4bfe9a80a2b86079c215ca755:

  dm: flush queued bios when process blocks to avoid deadlock (2017-02-17 00:54:10 -0500)

are available in the git repository at:

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

for you to fetch changes up to 2664f3c94abc7181171b7c05b2aaa76ea7d9d613:

  dm raid: bump the target version (2017-02-28 16:47:52 -0500)

Please pull, thanks.
Mike

----------------------------------------------------------------
- A dm-raid stable@ fix for possible corruption when triggering a raid
  reshape via lvm2; and an additional small patch ontop to bump version
  of the dm-raid target outside of the stable@ fix

- A dm-raid fix for a 'dm-4.11-changes' regression introduced by a
  commit that was meant to only cleanup confusing branching.

----------------------------------------------------------------
Heinz Mauelshagen (1):
      dm raid: fix data corruption on reshape request

Mike Snitzer (2):
      dm raid: fix raid "check" regression due to improper cleanup in raid_message()
      dm raid: bump the target version

 drivers/md/dm-raid.c | 20 ++++++++++++++++----
 1 file changed, 16 insertions(+), 4 deletions(-)

                 reply	other threads:[~2017-03-02 15:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170302153916.GA35026@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=heinzm@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