commit 2d6f0600b2cd755959527230ef5a6fba97bb762a upstream.
vmx-crypto driver make use of some VSX instructions which are
only available if VSX is enabled. Running in cases where VSX
are not enabled vmx-crypto fails in a VSX exception.
In order to fix this enable_kernel_vsx() was added to turn on
V
From: Leonidas Da Silva Barbosa
commit 72cd7b44bc99376b3f3c93cedcd052663fcdf705 upstream.
enable_kernel_vsx() function was commented since anything was using
it. However, vmx-crypto driver uses VSX instructions which are
only available if VSX is enable. Otherwise it rises an exception oops.
Thi
From: Leonidas Da Silva Barbosa
commit 72cd7b44bc99376b3f3c93cedcd052663fcdf705 upstream.
enable_kernel_vsx() function was commented since anything was using
it. However, vmx-crypto driver uses VSX instructions which are
only available if VSX is enable. Otherwise it rises an exception oops.
Thi
From: Leonidas Da Silva Barbosa
commit 2d6f0600b2cd755959527230ef5a6fba97bb762a upstream.
vmx-crypto driver make use of some VSX instructions which are
only available if VSX is enabled. Running in cases where VSX
are not enabled vmx-crypto fails in a VSX exception.
In order to fix this enable_k
Commit a1efb01feca597b ("jump_label, locking/static_keys: Rename
JUMP_LABEL_TYPE_* and related helpers to the static_key* pattern")
introduced the definition of JUMP_TYPE_MASK in
include/linux/jump_label.h causing the following name collision:
In file included from drivers/crypto/caam/desc_const
This platform drivers have a OF device ID table but the OF module
alias information is not created so module autoloading won't work.
Signed-off-by: Luis de Bethencourt
---
drivers/char/hw_random/pasemi-rng.c | 1 +
drivers/char/hw_random/ppc4xx-rng.c | 1 +
2 files changed, 2 insertions(+)
diff
On 9/3/2015 9:21 PM, Fabio Estevam wrote:
> From: Fabio Estevam
>
> JUMP_TYPE_MASK is defined in desc.h and it is never used, so we can
> safely remove it to avoid the following build warning:
>
> In file included from drivers/crypto/caam/desc_constr.h:7:0,
> from drivers/crypto
Hello,
These patches add the missing MODULE_DEVICE_TABLE() for OF to export
the information so modules have the correct aliases built-in and
autoloading works correctly.
A longer explanation by Javier Canillas can be found here:
https://lkml.org/lkml/2015/7/30/519
Thanks,
Luis
Luis de Bethencou
On 09/15/2015 05:24 AM, Herbert Xu wrote:
>>> Change mpi_read_buffer to return a number without leading zeros
>>> > > so that mpi_read_buffer and mpi_get_buffer return the same thing.
>> >
>> > Hmmm... This would appear to have the undesirable side effect of causing 1
>> > out of 256 module signi
From: David Woodhouse
The GPL does not permit us to link against the OpenSSL library. Use
LGPL for sign-file and extract-file instead.
Reported-by: Julian Andres Klode
Signed-off-by: David Woodhouse
Signed-off-by: David Howells
Reviewed-by: Julian Andres Klode
---
scripts/extract-cert.c |
OMAP AES hw supports AES-GCM mode.
Adding support for GCM and RFC4106 GCM mode in omap-aes driver.
Signed-off-by: Lokesh Vutla
---
Tested on BeagleBone-Black: http://pastebin.ubuntu.com/12417512/
Changes since v1:
- Addressed comments by Herbert.
Previously posted here:
https://www.mail-archiv
On Tue, Sep 15, 2015 at 10:09:56AM +0100, David Howells wrote:
> Tadeusz Struk wrote:
>
> > Change mpi_read_buffer to return a number without leading zeros
> > so that mpi_read_buffer and mpi_get_buffer return the same thing.
>
> Hmmm... This would appear to have the undesirable side effect of
David Howells wrote:
> > Change mpi_read_buffer to return a number without leading zeros
> > so that mpi_read_buffer and mpi_get_buffer return the same thing.
>
> Hmmm... This would appear to have the undesirable side effect of causing 1
> out of 256 module signing keys to be unusable (ie. thos
Andy Whitcroft wrote:
> This leads us to truncate the id for kernel module signing keys and to
> fail to recognise our own modules:
>
> [1.572423] Loaded X.509 cert 'Build time autogenerated kernel
> key: 62a7c3d2da278be024da4af8652c071f3fea33'
> [1.646153] Request for unknown mo
Tadeusz Struk wrote:
> Change mpi_read_buffer to return a number without leading zeros
> so that mpi_read_buffer and mpi_get_buffer return the same thing.
Hmmm... This would appear to have the undesirable side effect of causing 1
out of 256 module signing keys to be unusable (ie. those that beg
15 matches
Mail list logo