linux-kernel - Re: [PATCH v2 1/3] crypto: Introduce notifier for new crypto algorithms

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180904133006.GA28715@lst.de>
Date:   Tue, 4 Sep 2018 15:30:06 +0200
From:   Torsten Duwe <duwe@....de>
To:     "Martin K. Petersen" <martin.petersen@...cle.com>
Cc:     herbert@...dor.apana.org.au, Jeff.Lien@....com,
        ard.biesheuvel@...aro.org, david.darrington@....com,
        hch@...radead.org, jeff.furlong@....com,
        linux-block@...r.kernel.org, linux-crypto@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
        tim.c.chen@...ux.intel.com
Subject: Re: [PATCH v2 1/3] crypto: Introduce notifier for new crypto
 algorithms

On Thu, Aug 30, 2018 at 11:00:14AM -0400, Martin K. Petersen wrote:
> Introduce a facility that can be used to receive a notification
> callback when a new algorithm becomes available. This can be used by
> existing crypto registrations to trigger a switch from a software-only
> algorithm to a hardware-accelerated version.

While this is apparently fine with the patch set you sent, what about
cases where the crypto context of old and new implementation is not
100% compatible? The switch will still work for sure if there are no
current active users of the algo, but otherwise...? Just a thought.

	Torsten