From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mx2.suse.de ([195.135.220.15]:53614 "EHLO mx1.suse.de"
        rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
        id S1726274AbeHWTBO (ORCPT <rfc822;stable@vger.kernel.org>);
        Thu, 23 Aug 2018 15:01:14 -0400
Date: Thu, 23 Aug 2018 17:31:01 +0200
From: Petr Vorel <pvorel@suse.cz>
To: Herbert Xu <herbert@gondor.apana.org.au>,
        Paulo Flabiano Smorigo <pfsmorigo@linux.vnet.ibm.com>
Cc: stable@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Backport e666d4e9ceec crypto: vmx - Use skcipher for ctr fallback
Message-ID: <20180823153101.GA27143@dell5510>
Reply-To: Petr Vorel <pvorel@suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

Hi,

I wonder, it it makes sense to backport commit
e666d4e9ceec crypto: vmx - Use skcipher for ctr fallback
to v 4.14 stable kernel.
I'm using it in 4.12+.

These commits (somehow similar) has been backported to 4.10.2:
5839f555fa57 crypto: vmx - Use skcipher for xts fallback
c96d0a1c47ab crypto: vmx - Use skcipher for cbc fallback

Kind regards,
Petr