mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
	dm-devel@redhat.com, linux-kernel@vger.kernel.org,
	Heinz Mauelshagen <heinzm@redhat.com>,
	Joe Thornber <ejt@redhat.com>, Mike Snitzer <snitzer@redhat.com>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Paul Taysom <taysom@chromium.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	stable@vger.kernel.org
Subject: [git pull] device-mapper fixes for 3.9
Date: Thu, 21 Mar 2013 02:26:26 +0000	[thread overview]
Message-ID: <20130321022625.GA25054@agk-dp.fab.redhat.com> (raw)

Please pull from:

  git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm tags/dm-3.9-fixes

to get the following device-mapper fixes for 3.9.

Thanks,
Alasdair

----------------------------------------------------------------
A set of device-mapper fixes for 3.9.

Fix reported data loss with discards and thin snapshots; avoid a
deadlock observed in dm verity; fix a race in the new dm cache code
along with some other minor bugs; store the cache policy version on disk
to make the stored hints format future-proof.

----------------------------------------------------------------
Heinz Mauelshagen (2):
      dm cache: detect cache_create failure
      dm cache: avoid calling policy destructor twice on error

Joe Thornber (5):
      dm thin: fix discard corruption
      dm thin: fix non power of two discard granularity calc
      dm cache: avoid 64 bit division on 32 bit
      dm cache: metadata clear dirty bits on clean shutdown
      dm cache: fix race in writethrough implementation

Mike Snitzer (2):
      dm cache: policy change version from string to integer set
      dm cache: policy ignore hints if generated by different version

Mikulas Patocka (1):
      dm verity: avoid deadlock

 drivers/md/dm-bufio.c                        |    2 +
 drivers/md/dm-cache-metadata.c               |   64 ++++++++--
 drivers/md/dm-cache-metadata.h               |    2 +-
 drivers/md/dm-cache-policy-cleaner.c         |    7 +-
 drivers/md/dm-cache-policy-internal.h        |    2 +
 drivers/md/dm-cache-policy-mq.c              |    8 +-
 drivers/md/dm-cache-policy.c                 |    8 ++
 drivers/md/dm-cache-policy.h                 |    2 +
 drivers/md/dm-cache-target.c                 |  169 +++++++++++++++++---------
 drivers/md/dm-thin.c                         |   11 +-
 drivers/md/dm-verity.c                       |   39 +++++-
 drivers/md/persistent-data/dm-btree-remove.c |   46 +++----
 12 files changed, 252 insertions(+), 108 deletions(-)

             reply	other threads:[~2013-03-21  2:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21  2:26 Alasdair G Kergon [this message]
2013-03-22 18:53 ` Darrick J. Wong
2013-03-22 20:14   ` [dm-devel] " Darrick J. Wong
2013-04-06  1:47 ` [git pull] device-mapper fixes for 3.9-rc6 Alasdair G Kergon

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=20130321022625.GA25054@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --cc=heinzm@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=snitzer@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=taysom@chromium.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

all inboxes | Powered by JetHome®