public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org,
	Heinz Mauelshagen <heinzm@redhat.com>,
	Joe Thornber <ejt@redhat.com>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Hannes Reinecke <hare@suse.de>,
	"Alasdair G. Kergon" <agk@redhat.com>
Subject: [git pull] device mapper fixes to include in 3.14-rc5
Date: Fri, 28 Feb 2014 13:03:37 -0500	[thread overview]
Message-ID: <20140228180335.GA27146@redhat.com> (raw)

The following changes since commit 6d0abeca3242a88cab8232e4acd7e2bf088f3bc2:

  Linux 3.14-rc3 (2014-02-16 13:30:25 -0800)

are available in the git repository at:

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

for you to fetch changes up to e0d849fad746cb36a6822e4595d8ba9bf0adf7fa:

  dm cache: fix truncation bug when mapping I/O to >2TB fast device (2014-02-28 09:23:02 -0500)

There will likely be additional dm-thin metadata and data resize fixes
to include in 3.14-rc6 next week.  But please pull for the following
fixes.

Thanks,
Mike

p.s.
Note to stable-minded folks: Immutable biovecs were introduced in 3.14,
so the related fixups for dm mirror are not needed in stable@ kernels.

----------------------------------------------------------------
A few dm-cache fixes, an invalid ioctl handling fix for dm multipath, a
couple immutable biovec fixups for dm mirror, and a few dm-thin fixes.

----------------------------------------------------------------
Hannes Reinecke (1):
      dm mpath: fix stalls when handling invalid ioctls

Heinz Mauelshagen (1):
      dm cache: fix truncation bug when mapping I/O to >2TB fast device

Mike Snitzer (5):
      dm cache: move hook_info into common portion of per_bio_data structure
      dm cache: do not add migration to completed list before unhooking bio
      dm thin: avoid metadata commit if a pool's thin devices haven't changed
      dm thin: fix the error path for the thin device constructor
      dm thin: allow metadata space larger than supported to go unused

Mikulas Patocka (2):
      dm io: fix I/O to multiple destinations
      dm raid1: fix immutable biovec related BUG when retrying read bio

 drivers/md/dm-cache-target.c                       | 13 +++++---
 drivers/md/dm-io.c                                 | 23 ++++++-------
 drivers/md/dm-mpath.c                              |  7 ++--
 drivers/md/dm-raid1.c                              |  3 ++
 drivers/md/dm-thin-metadata.c                      | 21 ++++++++++--
 drivers/md/dm-thin-metadata.h                      | 10 +++---
 drivers/md/dm-thin.c                               | 39 ++++++++++++++--------
 drivers/md/persistent-data/dm-space-map-metadata.c |  2 ++
 drivers/md/persistent-data/dm-space-map-metadata.h | 11 ++++++
 9 files changed, 89 insertions(+), 40 deletions(-)

                 reply	other threads:[~2014-02-28 18:03 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=20140228180335.GA27146@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --cc=hare@suse.de \
    --cc=heinzm@redhat.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox