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>,
Milan Broz <gmazyland@gmail.com>
Subject: [git pull] device mapper fixes for 5.9 final
Date: Wed, 23 Sep 2020 13:30:24 -0400 [thread overview]
Message-ID: <20200923173024.GA97173@lobo> (raw)
Hi Linus,
The following changes since commit beaeb4f39bc31d5a5eb6d05465a86af4fe147732:
Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm (2020-09-21 08:53:48 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git tags/for-5.9/dm-fixes-2
for you to fetch changes up to 4c07ae0ad493b7b2d3dd3e53870e594f136ce8a5:
dm crypt: document encrypted keyring key option (2020-09-22 13:25:58 -0400)
Please pull, thanks!
Mike
----------------------------------------------------------------
- DM core fix for incorrect double bio splitting. Keep "fixing" this
because past attempts didn't fully appreciate the liability relative
to recursive bio splitting. This fix limits DM's bio splitting to a
single method and does _not_ use blk_queue_split() for normal IO.
- DM crypt Documentation updates for features added during 5.9 merge.
----------------------------------------------------------------
Mike Snitzer (2):
dm: fix bio splitting and its bio completion order for regular IO
dm: fix comment in dm_process_bio()
Milan Broz (2):
dm crypt: document new no_workqueue flags
dm crypt: document encrypted keyring key option
.../admin-guide/device-mapper/dm-crypt.rst | 10 +++++++-
drivers/md/dm.c | 27 ++++------------------
2 files changed, 14 insertions(+), 23 deletions(-)
next reply other threads:[~2020-09-23 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 17:30 Mike Snitzer [this message]
2020-09-23 21:54 ` [git pull] device mapper fixes for 5.9 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=20200923173024.GA97173@lobo \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=linux-block@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).