Eric Lee / smarc-fsl-linux-kernel

21 May, 2019

1 commit

  • 1ccea77e2   treewide: Replace GPLv2 boilerplate/reference with SPDX - rule 13 ... Browse Code »

    Based on 2 normalized pattern(s):

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license as published by
    the free software foundation either version 2 of the license or at
    your option any later version this program is distributed in the
    hope that it will be useful but without any warranty without even
    the implied warranty of merchantability or fitness for a particular
    purpose see the gnu general public license for more details you
    should have received a copy of the gnu general public license along
    with this program if not see http www gnu org licenses

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license as published by
    the free software foundation either version 2 of the license or at
    your option any later version this program is distributed in the
    hope that it will be useful but without any warranty without even
    the implied warranty of merchantability or fitness for a particular
    purpose see the gnu general public license for more details [based]
    [from] [clk] [highbank] [c] you should have received a copy of the
    gnu general public license along with this program if not see http
    www gnu org licenses

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-or-later

    has been chosen to replace the boilerplate/reference in 355 file(s).

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Kate Stewart
    Reviewed-by: Jilayne Lovejoy
    Reviewed-by: Steve Winslow
    Reviewed-by: Allison Randal
    Cc: linux-spdx@vger.kernel.org
    Link: https://lkml.kernel.org/r/20190519154041.837383322@linutronix.de
    Signed-off-by: Greg Kroah-Hartman

    Thomas Gleixner
     

22 Mar, 2019

2 commits

  • 8b8d91d4c   crypto: simd - convert to use crypto_simd_usable() ... Browse Code »

    Replace all calls to may_use_simd() in the shared SIMD helpers with
    crypto_simd_usable(), in order to allow testing the no-SIMD code paths.

    Signed-off-by: Eric Biggers
    Reviewed-by: Ard Biesheuvel
    Signed-off-by: Herbert Xu

    Eric Biggers
     
  • 1661131a0   crypto: simd - support wrapping AEAD algorithms ... Browse Code »

    Update the crypto_simd module to support wrapping AEAD algorithms.
    Previously it only supported skciphers. The code for each is similar.

    I'll be converting the x86 implementations of AES-GCM, AEGIS, and MORUS
    to use this. Currently they each independently implement the same
    functionality. This will not only simplify the code, but it will also
    fix the bug detected by the improved self-tests: the user-provided
    aead_request is modified. This is because these algorithms currently
    reuse the original request, whereas the crypto_simd helpers build a new
    request in the original request's context.

    Signed-off-by: Eric Biggers
    Signed-off-by: Herbert Xu

    Eric Biggers
     

09 Nov, 2018

1 commit

  • 508a1c4df   crypto: simd - correctly take reqsize of wrapped skcipher into account ... Browse Code »

    The simd wrapper's skcipher request context structure consists
    of a single subrequest whose size is taken from the subordinate
    skcipher. However, in simd_skcipher_init(), the reqsize that is
    retrieved is not from the subordinate skcipher but from the
    cryptd request structure, whose size is completely unrelated to
    the actual wrapped skcipher.

    Reported-by: Qian Cai
    Signed-off-by: Ard Biesheuvel
    Tested-by: Qian Cai
    Signed-off-by: Herbert Xu

    Ard Biesheuvel
     

03 Mar, 2018

1 commit

  • d14f0a1fc   crypto: simd - allow registering multiple algorithms at once ... Browse Code »

    Add a function to crypto_simd that registers an array of skcipher
    algorithms, then allocates and registers the simd wrapper algorithms for
    them. It assumes the naming scheme where the names of the underlying
    algorithms are prefixed with two underscores.

    Also add the corresponding 'unregister' function.

    Most of the x86 crypto modules will be able to use these.

    Signed-off-by: Eric Biggers
    Signed-off-by: Herbert Xu

    Eric Biggers
     

29 Nov, 2017

1 commit

28 Nov, 2016

1 commit