Linux Device Mapper development
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ondrej Kozina <okozina@redhat.com>,
	dm-devel@redhat.com, Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fixes for 4.10-rc7
Date: Fri, 3 Feb 2017 14:11:08 -0500	[thread overview]
Message-ID: <20170203191108.GA3796@redhat.com> (raw)

Hi Linus,

The following changes since commit 566cf877a1fcb6d6dc0126b076aad062054c2637:

  Linux 4.10-rc6 (2017-01-29 14:25:17 -0800)

are available in the git repository at:

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

for you to fetch changes up to f5b0cba8f23915e92932f11eb063e37d70556a89:

  dm crypt: replace RCU read-side section with rwsem (2017-02-03 10:26:14 -0500)

Please pull, thanks.
Mike

----------------------------------------------------------------
- A fix for a race in .request_fn request-based DM request handling vs
  DM device destruction

- An RCU fix for dm-crypt's kernel keyring support that was included in
  4.10-rc1

- A -Wbool-operation warning fix for DM multipath

----------------------------------------------------------------
Mike Snitzer (2):
      dm mpath: cleanup -Wbool-operation warning in choose_pgpath()
      dm rq: cope with DM device destruction while in dm_old_request_fn()

Ondrej Kozina (1):
      dm crypt: replace RCU read-side section with rwsem

 drivers/md/dm-crypt.c | 8 ++++----
 drivers/md/dm-mpath.c | 4 ++--
 drivers/md/dm-rq.c    | 4 ++++
 3 files changed, 10 insertions(+), 6 deletions(-)

             reply	other threads:[~2017-02-03 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 19:11 Mike Snitzer [this message]
2017-02-04  0:18 ` [git pull] device mapper fixes for 4.10-rc7 Linus Torvalds
2017-02-06 20:48   ` 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=20170203191108.GA3796@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=okozina@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox