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>,
	Heinz Mauelshagen <heinzm@redhat.com>,
	Pavitra Kumar <pavitrak@nvidia.com>
Subject: [git pull] device mapper fixes for 3.18
Date: Wed, 12 Nov 2014 19:34:26 -0500	[thread overview]
Message-ID: <20141113003425.GA9508@redhat.com> (raw)

Hi Linus,

The following changes since commit 56ec16cb1e1ce46354de8511eef962a417c32c92:

  dm log userspace: fix memory leak in dm_ulog_tfr_init failure path (2014-10-05 20:03:38 -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.18-fixes

for you to fetch changes up to 9b460d3699324d570a4d4161c3741431887f102f:

  dm btree: fix a recursion depth bug in btree walking code (2014-11-10 15:23:58 -0500)

Please pull, thanks.
Mike

----------------------------------------------------------------
. stable fix for dm-thin that avoids normal IO racing with discard

. stable fix for a dm-cache related bug in dm-btree walking code that
  results from using very large fast device (e.g. 4T) with a very small
  cache blocksize (e.g. 32K) -- this is a very uncommon configuration

. a couple fixes for dm-raid (one for stable and the other addresses a
  crash in 3.18-rc1 code)

. stable fix for dm-thinp that addresses a very rare dm-bufio bug having
  to do with memory reclaimation (via shrinker) when using dm-thinp
  ontop of loopback devices

. fix a leak in dm-stripe target constructor's error path

----------------------------------------------------------------
Heinz Mauelshagen (2):
      dm raid: ensure superblock's size matches device's logical block size
      dm raid: fix inaccessible superblocks causing oops in configure_discard_support

Joe Thornber (2):
      dm thin: grab a virtual cell before looking up the mapping
      dm btree: fix a recursion depth bug in btree walking code

Mikulas Patocka (1):
      dm bufio: change __GFP_IO to __GFP_FS in shrinker callbacks

Pavitra Kumar (1):
      dm stripe: fix potential for leak in stripe_ctr error path

 drivers/md/dm-bufio.c                          | 12 ++++++------
 drivers/md/dm-raid.c                           | 17 ++++++++++++-----
 drivers/md/dm-stripe.c                         |  4 +++-
 drivers/md/dm-thin.c                           | 16 ++++++++++++----
 drivers/md/persistent-data/dm-btree-internal.h |  6 ++++++
 drivers/md/persistent-data/dm-btree-spine.c    |  2 +-
 drivers/md/persistent-data/dm-btree.c          | 24 ++++++++++--------------
 7 files changed, 50 insertions(+), 31 deletions(-)

             reply	other threads:[~2014-11-13  0:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13  0:34 Mike Snitzer [this message]
2014-11-24 16:47 ` [git pull] device mapper fixes for 3.18 Mikulas Patocka
2014-11-24 18:43   ` Mike Snitzer

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=20141113003425.GA9508@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.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=pavitrak@nvidia.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.