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>,
	Milan Broz <gmazyland@gmail.com>
Subject: [git pull] device mapper fixes for 3.15-rc4
Date: Fri, 2 May 2014 15:24:18 -0400	[thread overview]
Message-ID: <20140502192417.GA23866@redhat.com> (raw)

The following changes since commit 0596661f0a16d9d69bf1033320e70b6ff52b5e81:

  dm cache: fix a lock-inversion (2014-04-04 14:53:05 -0400)

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

for you to fetch changes up to 131cd131a9ff63d4b84f3fe15073a2984ac30066:

  dm cache: fix writethrough mode quiescing in cache_map (2014-05-01 16:14:24 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
A few dm-thinp fixes for changes merged in 3.15-rc1.

A dm-verity fix for an immutable biovec regression that affects 3.14+.

A dm-cache fix to properly quiesce when using writethrough mode (3.14+).

----------------------------------------------------------------
Joe Thornber (2):
      dm thin: irqsave must always be used with the pool->lock spinlock
      dm thin: fix rcu_read_lock being held in code that can sleep

Mike Snitzer (2):
      dm thin: use INIT_WORK_ONSTACK in noflush_work to avoid ODEBUG warning
      dm cache: fix writethrough mode quiescing in cache_map

Milan Broz (1):
      dm verity: fix biovecs hash calculation regression

 drivers/md/dm-cache-target.c |  1 +
 drivers/md/dm-thin.c         | 77 ++++++++++++++++++++++++++++++++++++++++----
 drivers/md/dm-verity.c       | 15 +++++----
 3 files changed, 81 insertions(+), 12 deletions(-)

                 reply	other threads:[~2014-05-02 19:24 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=20140502192417.GA23866@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-kernel@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 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.