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, Joe Thornber <ejt@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] last couple device mapper fixes for 3.19 final
Date: Thu, 29 Jan 2015 08:49:27 -0500	[thread overview]
Message-ID: <20150129134927.GA663@redhat.com> (raw)

Hi Linus,

The following changes since commit 26bc420b59a38e4e6685a73345a0def461136dce:

  Linux 3.19-rc6 (2015-01-25 20:04:41 -0800)

are available in the git repository at:

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

for you to fetch changes up to 2a7eaea02b99b6e267b1e89c79acc6e9a51cee3b:

  dm thin: don't allow messages to be sent to a pool target in READ_ONLY or FAIL mode (2015-01-28 10:00:34 -0500)

Please pull, thanks.
Mike

----------------------------------------------------------------
1 stable fix for a dm-cache 3.19-rc6 regression and 1 stable fix for
dm-thin:

- fix DM cache metadata open/lookup error paths to properly use ERR_PTR
  and IS_ERR (fixes: 3.19-rc6 "stable" commit 9b1cc9f251)

- fix DM thin-provisioning to disallow userspace from sending messages
  to the thin-pool if the pool is in READ_ONLY or FAIL mode since no
  metadata changes are not allowed in these modes.

----------------------------------------------------------------
Joe Thornber (2):
      dm cache: fix missing ERR_PTR returns and handling
      dm thin: don't allow messages to be sent to a pool target in READ_ONLY or FAIL mode

 drivers/md/dm-cache-metadata.c | 9 +++++----
 drivers/md/dm-thin.c           | 6 ++++++
 2 files changed, 11 insertions(+), 4 deletions(-)

                 reply	other threads:[~2015-01-29 13:49 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=20150129134927.GA663@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@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.