All of lore.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,
	Alasdair G Kergon <agk@redhat.com>, Joe Thornber <ejt@redhat.com>,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: [git pull] device mapper fixes for 3.15-rc6
Date: Fri, 16 May 2014 10:51:15 -0400	[thread overview]
Message-ID: <20140516145115.GA29451@redhat.com> (raw)

The following changes since commit d6d211db37e75de2ddc3a4f979038c40df7cc79c:

  Linux 3.15-rc5 (2014-05-09 13:10:52 -0700)

are available in the git repository at:

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

for you to fetch changes up to 4cdd2ad78098244c1bc9ec4374ea1c225fd1cd6f:

  dm mpath: fix lock order inconsistency in multipath_ioctl (2014-05-14 16:12:17 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
A dm-crypt fix for a cpu hotplug crash that switches from using per-cpu
data to a mempool allocation (which offers allocation with cpu locality,
and there is no inter-cpu communication on slab allocation).

A couple dm-thinp stable fixes to address "out-of-data-space" issues.

A dm-multipath fix for a LOCKDEP warning introduced in 3.15-rc1.

----------------------------------------------------------------
Joe Thornber (2):
      dm thin: allow metadata commit if pool is in PM_OUT_OF_DATA_SPACE mode
      dm thin: add timeout to stop out-of-data-space mode holding IO forever

Mike Snitzer (1):
      dm mpath: fix lock order inconsistency in multipath_ioctl

Mikulas Patocka (1):
      dm crypt: fix cpu hotplug crash by removing per-cpu structure

 drivers/md/dm-crypt.c | 61 ++++++++++-----------------------------------------
 drivers/md/dm-mpath.c |  2 +-
 drivers/md/dm-thin.c  | 23 ++++++++++++++++++-
 3 files changed, 35 insertions(+), 51 deletions(-)

                 reply	other threads:[~2014-05-16 14:51 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=20140516145115.GA29451@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.