This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1666483
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1666483
Title:
ecryptfs fails to load block cipher on ppc64el
Status in linux package in Ubuntu:
Incomplete
Bug description:
Specifically, this is not an ecryptfs issue. ecryptfs attempts to
load the CBC AES block cipher and the ppc64el specific vmx_crypto
crypto driver gets loaded. However, this is using the older blkcipher
API rather than the newer skcipher API as introduced by the following
commit in 4.10:
commit 79c65d179a40e145287e59b33dc782a7c4bf0986
Author: Herbert Xu <[email protected]>
Date: Tue Nov 22 20:08:39 2016 +0800
crypto: cbc - Convert to skcipher
This patch converts cbc over to the skcipher interface. It also
rearranges the code to allow it to be reused by drivers.
We see the following error:
Feb 20 16:57:53 gulpin kernel: Failed to allocate transformation for
'cbc(aes)': -2
Feb 20 16:57:53 gulpin kernel: ecryptfs_init_crypt_ctx: cryptfs:
init_crypt_ctx(): Error initializing cipher [cbc(aes)]
Feb 20 16:57:53 gulpin kernel: ecryptfs_new_file_context: Error initializing
cryptographic context for cipher [aes]: rc = [-2]
Feb 20 16:57:53 gulpin kernel: ecryptfs_initialize_file: Error creating new
file context; rc = [-2]
Feb 20 16:57:53 gulpin kernel: Failed to allocate transformation for
'cbc(aes)': -2
Loading the software based cbc crypto before starting ecryptfs rather
than the optimized vmx_crypto allows ecryptfs to run correctly.
So, this core issue is that we need vmx_crypto updated to the newer
crypto API to resolve this issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666483/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
