From: Milan Broz <gmazyland@gmail.com>
To: "EXTERNAL D Sharmila (Iwave,
RBEI/PAC-PF)" <external.Sharmila.D@in.bosch.com>,
"dm-crypt@saout.de" <dm-crypt@saout.de>
Subject: Re: [dm-crypt] IV generation for dm-crypt
Date: Wed, 29 Jan 2020 11:39:15 +0100 [thread overview]
Message-ID: <a65ee88e-23dc-bede-01ed-b72e105aba85@gmail.com> (raw)
In-Reply-To: <7d768fdce86cdd4ac6468dd606bd03b7048b6a05.camel@bosch.com>
On 29/01/2020 11:28, EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF) wrote:
> After digging into the issue I found some patch regarding kernel dm-
> crypt driver. Can you please provide me the input on this, weather this
> patch will be helpful?
>
> https://lore.kernel.org/patchwork/patch/777700/
This patch is obsolete. There was a discussion if we need to move all IV generators
to core crypto library, currently mainline kernel moved ESSIV only
(because it is used also in fscrypt), the rest remains in dm-crypt.
There is no change in behaviour except the new dependence on "essiv.ko" module.
If you have an older kernel, you do not need to apply anything, it was
just code cleaning (and avoiding code duplication).
m.
next prev parent reply other threads:[~2020-01-29 10:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 8:18 [dm-crypt] IV generation for dm-crypt EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF)
2020-01-29 9:48 ` Milan Broz
2020-01-29 10:28 ` EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF)
2020-01-29 10:39 ` Milan Broz [this message]
2020-01-29 10:36 ` [dm-crypt] Data corruption of encrypted partition EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF)
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=a65ee88e-23dc-bede-01ed-b72e105aba85@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=external.Sharmila.D@in.bosch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox