public inbox for linux-block@vger.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, linux-block@vger.kernel.org,
	Alasdair G Kergon <agk@redhat.com>,
	Mikulas Patocka <mpatocka@redhat.com>,
	Nikos Tsironis <ntsironis@arrikto.com>
Subject: [git pull] device mapper fixes for 5.0 final
Date: Fri, 15 Feb 2019 09:38:32 -0500	[thread overview]
Message-ID: <20190215143832.GA20900@redhat.com> (raw)

Hi Linus,

The following changes since commit d13937116f1e82bf508a6325111b322c30c85eb9:

  Linux 5.0-rc6 (2019-02-10 14:42:20 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 4ae280b4ee3463fa57bbe6eede26b97daff8a0f1:

  dm thin: fix bug where bio that overwrites thin block ignores FUA (2019-02-14 19:02:29 -0500)

Please pull, thanks.
Mike

----------------------------------------------------------------
- Fix bug in DM crypt's sizing of its block integrity tag space,
  resulting in less memory use when DM crypt layers on DM integrity.

- Fix a long-standing DM thinp crash consistency bug that was due to
  improper handling of FUA.  This issue is specific to writes that
  fill an entire thinp block which needs to be allocated.

----------------------------------------------------------------
Mikulas Patocka (1):
      dm crypt: don't overallocate the integrity tag space

Nikos Tsironis (1):
      dm thin: fix bug where bio that overwrites thin block ignores FUA

 drivers/md/dm-crypt.c |  2 +-
 drivers/md/dm-thin.c  | 55 ++++++++++++++++++++++++++++++++++++++++++++++-----
 2 files changed, 51 insertions(+), 6 deletions(-)

             reply	other threads:[~2019-02-15 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 14:38 Mike Snitzer [this message]
2019-02-15 17:10 ` [git pull] device mapper fixes for 5.0 final pr-tracker-bot

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=20190215143832.GA20900@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=ntsironis@arrikto.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