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, Mikulas Patocka <mpatocka@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fixes for 4.6-rc4
Date: Thu, 14 Apr 2016 17:51:42 -0400	[thread overview]
Message-ID: <20160414215142.GA21120@redhat.com> (raw)

Hi Linus,

The following changes since commit bf16200689118d19de1b8d2a3c314fc21f5dc7bb:

  Linux 4.6-rc3 (2016-04-10 17:58:30 -0700)

are available in the git repository at:

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

for you to fetch changes up to 9567366fefddeaea4ed1d713270535d93a3b3c76:

  dm cache metadata: fix READ_LOCK macros and cleanup WRITE_LOCK macros (2016-04-14 17:34:49 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- fix a 4.6-rc1 bio-based DM 'struct dm_target_io' leak in an error path

- stable@ fix for DM cache metadata's READ_LOCK macros that were
  incorrectly returning error if the block manager was in read-only
  mode; also cleanup multi-statement macros to use do {} while(0)

----------------------------------------------------------------
Mike Snitzer (1):
      dm cache metadata: fix READ_LOCK macros and cleanup WRITE_LOCK macros

Mikulas Patocka (1):
      dm: fix dm_target_io leak if clone_bio() returns an error

 drivers/md/dm-cache-metadata.c | 64 ++++++++++++++++++++++++++----------------
 drivers/md/dm.c                |  4 ++-
 2 files changed, 43 insertions(+), 25 deletions(-)

                 reply	other threads:[~2016-04-14 21: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=20160414215142.GA21120@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --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.