From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com
 [IPv6:2a00:1450:4864:20::441])
 (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by mail.server123.net (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Wed, 29 Jan 2020 11:39:17 +0100 (CET)
Received: by mail-wr1-x441.google.com with SMTP id z3so19594107wru.3
 for <dm-crypt@saout.de>; Wed, 29 Jan 2020 02:39:17 -0800 (PST)
References: <c5b4597d1f486e0d11f4c5ef83a5a6b0691a5fc9.camel@bosch.com>
 <90067aa3-111f-f144-389a-574007fd4e6b@gmail.com>
 <7d768fdce86cdd4ac6468dd606bd03b7048b6a05.camel@bosch.com>
From: Milan Broz <gmazyland@gmail.com>
Message-ID: <a65ee88e-23dc-bede-01ed-b72e105aba85@gmail.com>
Date: Wed, 29 Jan 2020 11:39:15 +0100
MIME-Version: 1.0
In-Reply-To: <7d768fdce86cdd4ac6468dd606bd03b7048b6a05.camel@bosch.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] IV generation for dm-crypt
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <https://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <https://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <https://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: "EXTERNAL D Sharmila (Iwave, RBEI/PAC-PF)" <external.Sharmila.D@in.bosch.com>, "dm-crypt@saout.de" <dm-crypt@saout.de>

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.