From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeffy Chen <jeffy.chen@rock-chips.com>,
dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
Milan Broz <gmazyland@gmail.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fixes for 4.14-rc4
Date: Thu, 5 Oct 2017 16:32:48 -0400 [thread overview]
Message-ID: <20171005203248.GA6858@redhat.com> (raw)
Hi Linus,
The following changes since commit e19b205be43d11bff638cad4487008c48d21c103:
Linux 4.14-rc2 (2017-09-24 16:38:56 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-4.14/dm-fixes
for you to fetch changes up to 41dcf197ad5373a7dd0a4b6572aec2e3ec6a0e49:
dm raid: fix incorrect status output at the end of a "recover" process (2017-10-05 16:21:30 -0400)
Please pull, thanks!
Mike
----------------------------------------------------------------
- A stable fix for the alignment of the event number reported at the
end of the 'DM_LIST_DEVICES' ioctl.
- A couple stable fixes for the DM crypt target.
- A DM raid health status reporting fix.
----------------------------------------------------------------
Jeffy Chen (1):
dm crypt: fix memory leak in crypt_ctr_cipher_old()
Jonathan Brassow (1):
dm raid: fix incorrect status output at the end of a "recover" process
Mikulas Patocka (1):
dm ioctl: fix alignment of event number in the device list
Milan Broz (1):
dm crypt: reject sector_size feature if device length is not aligned to it
Documentation/device-mapper/dm-raid.txt | 1 +
drivers/md/dm-core.h | 1 +
drivers/md/dm-crypt.c | 5 +++++
drivers/md/dm-ioctl.c | 37 +++++++++++++++++++++------------
drivers/md/dm-raid.c | 11 +++++-----
drivers/md/dm.c | 10 +++++++--
include/uapi/linux/dm-ioctl.h | 4 ++--
7 files changed, 47 insertions(+), 22 deletions(-)
reply other threads:[~2017-10-05 20:32 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=20171005203248.GA6858@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=jeffy.chen@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox