From: Milan Broz <gmazyland@gmail.com>
To: dm-devel@redhat.com
Cc: Milan Broz <gmazyland@gmail.com>
Subject: [PATCH 0/7] Data integrity protection with dm-integrity and dm-crypt
Date: Thu, 16 Mar 2017 15:39:37 +0100 [thread overview]
Message-ID: <20170316143944.19843-1-gmazyland@gmail.com> (raw)
In-Reply-To: <cover.1483551181.git.gmazyland@gmail.com>
These are additional patches to previously submitted integrity protection commits,
based on for-next branch in Mike's DM tree.
Most of them probably can be folded-in, patches are separated for better readability.
The last patch for large encryption sectors is a new feature but because it depends
on all previous patches it is posted in this series.
Milan Broz (7):
dm-crypt: Fix documentation of integrity table option.
dm-crypt: Move IV constructor to separate function.
dm-crypt: Introduce new format of cipher with capi: prefix.
dm-crypt: Compute HMAC key size in a separate function.
dm-crypt: Parse cipher specification according to AEAD flag.
dm-crypt: Remove obsolete integrity_mode function.
dm-crypt: optionally support larger encryption sector size
Documentation/device-mapper/dm-crypt.txt | 65 +++--
drivers/md/dm-crypt.c | 479 +++++++++++++++++++++----------
2 files changed, 371 insertions(+), 173 deletions(-)
--
2.11.0
next prev parent reply other threads:[~2017-03-16 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 19:23 [RFC PATCH 0/4] Data integrity protection with dm-integrity and dm-crypt Milan Broz
2017-01-04 19:23 ` [RFC PATCH 1/4] dm-table: Add flag to allow own target handling of integrity metadata Milan Broz
2017-01-04 19:23 ` [RFC PATCH 2/4] Add sector start offset to dm-bufio interface Milan Broz
2017-01-04 19:23 ` [RFC PATCH 3/4] Add the dm-integrity target Milan Broz
2017-01-04 19:23 ` [RFC PATCH 4/4] Add cryptographic data integrity protection (authenticated encryption) to dm-crypt Milan Broz
2017-03-16 14:39 ` Milan Broz [this message]
2017-03-16 19:12 ` [PATCH 0/7] Data integrity protection with dm-integrity and dm-crypt Mike Snitzer
2017-03-16 14:39 ` [PATCH 1/7] dm-crypt: Fix documentation of integrity table option Milan Broz
2017-03-16 14:39 ` [PATCH 2/7] dm-crypt: Move IV constructor to separate function Milan Broz
2017-03-16 14:39 ` [PATCH 3/7] dm-crypt: Introduce new format of cipher with capi: prefix Milan Broz
2017-03-16 14:39 ` [PATCH 4/7] dm-crypt: Compute HMAC key size in a separate function Milan Broz
2017-03-16 14:39 ` [PATCH 5/7] dm-crypt: Parse cipher specification according to AEAD flag Milan Broz
2017-03-16 14:39 ` [PATCH 6/7] dm-crypt: Remove obsolete integrity_mode function Milan Broz
2017-03-16 14:39 ` [PATCH 7/7] dm-crypt: optionally support larger encryption sector size Milan Broz
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=20170316143944.19843-1-gmazyland@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-devel@redhat.com \
/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.