From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
Kees Cook <keescook@chromium.org>
Subject: [git pull] device mapper fixes for 4.17-rc5
Date: Thu, 10 May 2018 11:56:59 -0400 [thread overview]
Message-ID: <20180510155658.GA20132@redhat.com> (raw)
Hi Linus,
The following changes since commit 6da6c0db5316275015e8cc2959f12a17584aeb64:
Linux v4.17-rc3 (2018-04-29 14:17:42 -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.17/dm-fixes
for you to fetch changes up to 28700a36232ba61fb6ac59466821546cb25aec69:
dm thin: update Documentation to clarify when "read_only" is valid (2018-05-10 11:18:49 -0400)
Please pull, thanks.
Mike
----------------------------------------------------------------
- A stable fix for DM integrity to use kvfree.
- Fix for a 4.17-rc1 change to dm-bufio's buffer alignment.
- Fixes for a few sparse warnings.
- Remove VLA usage in DM mirror target.
- Improve DM thinp Documentation for the "read_only" feature.
----------------------------------------------------------------
Kees Cook (1):
dm mirror: remove VLA usage
Mike Snitzer (3):
dm cache background tracker: fix sparse warning
dm: fix some sparse warnings and whitespace in dax methods
dm thin: update Documentation to clarify when "read_only" is valid
Mikulas Patocka (2):
dm integrity: use kvfree for kvmalloc'd memory
dm bufio: fix buffer alignment
Documentation/device-mapper/thin-provisioning.txt | 5 ++++-
drivers/md/dm-bufio.c | 5 +++--
drivers/md/dm-cache-background-tracker.c | 2 +-
drivers/md/dm-integrity.c | 2 +-
drivers/md/dm-raid1.c | 10 ++++++----
drivers/md/dm.c | 7 ++++---
6 files changed, 19 insertions(+), 12 deletions(-)
reply other threads:[~2018-05-10 15:56 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=20180510155658.GA20132@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=keescook@chromium.org \
--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