All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junaid Shahid <junaids@google.com>, Jan Kara <jack@suse.cz>,
	Gilad Ben-Yossef <gilad@benyossef.com>,
	dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>
Subject: [git pull] device mapper fixes for 4.12-rc4
Date: Fri, 2 Jun 2017 13:16:41 -0400	[thread overview]
Message-ID: <20170602171640.GA59854@redhat.com> (raw)

Hi Linus,

The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:

  Linux 4.12-rc2 (2017-05-21 19:30:23 -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.12/dm-fixes-3

for you to fetch changes up to ff0361b34ac63ef80c785c32d62e0e9d89a2cf89:

  dm: make flush bios explicitly sync (2017-05-31 10:50:23 -0400)

Please pull, thanks.
Mike

----------------------------------------------------------------
- a DM verity fix for a mode when no salt is used

- a fix to DM to account for the possibility that PREFLUSH or FUA are
  used without the SYNC flag if the underlying storage doesn't have a
  volatile write-cache

- a DM ioctl memory allocation flag fix to use __GFP_HIGH to allow
  emergency forward progress (by using memory reserves as last resort)

- a small DM integrity cleanup to use kvmalloc() instead of duplicating
  the same

----------------------------------------------------------------
Gilad Ben-Yossef (1):
      dm verity: fix no salt use case

Jan Kara (1):
      dm: make flush bios explicitly sync

Junaid Shahid (1):
      dm ioctl: restore __GFP_HIGH in copy_params()

Mikulas Patocka (1):
      dm integrity: use kvmalloc() instead of dm_integrity_kvmalloc()

 drivers/md/dm-bufio.c           |  2 +-
 drivers/md/dm-integrity.c       | 30 ++++++++----------------------
 drivers/md/dm-ioctl.c           |  5 +++--
 drivers/md/dm-raid1.c           |  2 +-
 drivers/md/dm-snap-persistent.c |  3 ++-
 drivers/md/dm-verity-target.c   |  4 ++--
 drivers/md/dm.c                 |  2 +-
 7 files changed, 18 insertions(+), 30 deletions(-)

                 reply	other threads:[~2017-06-02 17:16 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=20170602171640.GA59854@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=gilad@benyossef.com \
    --cc=jack@suse.cz \
    --cc=junaids@google.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.