License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 14:07:57 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2015-03-10 08:47:44 +00:00
|
|
|
|
|
|
|
|
menuconfig ARM_CRYPTO
|
|
|
|
|
bool "ARM Accelerated Cryptographic Algorithms"
|
|
|
|
|
depends on ARM
|
|
|
|
|
help
|
|
|
|
|
Say Y here to choose from a selection of cryptographic algorithms
|
|
|
|
|
implemented using ARM specific CPU features or instructions.
|
|
|
|
|
|
|
|
|
|
if ARM_CRYPTO
|
|
|
|
|
|
|
|
|
|
config CRYPTO_SHA1_ARM
|
|
|
|
|
tristate "SHA1 digest algorithm (ARM-asm)"
|
|
|
|
|
select CRYPTO_SHA1
|
|
|
|
|
select CRYPTO_HASH
|
|
|
|
|
help
|
|
|
|
|
SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
|
|
|
|
|
using optimized ARM assembler.
|
|
|
|
|
|
|
|
|
|
config CRYPTO_SHA1_ARM_NEON
|
|
|
|
|
tristate "SHA1 digest algorithm (ARM NEON)"
|
|
|
|
|
depends on KERNEL_MODE_NEON
|
|
|
|
|
select CRYPTO_SHA1_ARM
|
|
|
|
|
select CRYPTO_SHA1
|
|
|
|
|
select CRYPTO_HASH
|
|
|
|
|
help
|
|
|
|
|
SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
|
|
|
|
|
using optimized ARM NEON assembly, when NEON instructions are
|
|
|
|
|
available.
|
|
|
|
|
|
2015-03-10 08:47:45 +00:00
|
|
|
config CRYPTO_SHA1_ARM_CE
|
|
|
|
|
tristate "SHA1 digest algorithm (ARM v8 Crypto Extensions)"
|
2020-01-22 19:38:21 +00:00
|
|
|
depends on KERNEL_MODE_NEON
|
2015-03-10 08:47:45 +00:00
|
|
|
select CRYPTO_SHA1_ARM
|
|
|
|
|
select CRYPTO_HASH
|
|
|
|
|
help
|
|
|
|
|
SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2) implemented
|
|
|
|
|
using special ARMv8 Crypto Extensions.
|
2015-03-10 08:47:46 +00:00
|
|
|
|
|
|
|
|
config CRYPTO_SHA2_ARM_CE
|
|
|
|
|
tristate "SHA-224/256 digest algorithm (ARM v8 Crypto Extensions)"
|
2020-01-22 19:38:21 +00:00
|
|
|
depends on KERNEL_MODE_NEON
|
2015-04-09 10:55:43 +00:00
|
|
|
select CRYPTO_SHA256_ARM
|
2015-03-10 08:47:46 +00:00
|
|
|
select CRYPTO_HASH
|
|
|
|
|
help
|
|
|
|
|
SHA-256 secure hash standard (DFIPS 180-2) implemented
|
|
|
|
|
using special ARMv8 Crypto Extensions.
|
2015-03-10 08:47:45 +00:00
|
|
|
|
2015-04-03 10:03:40 +00:00
|
|
|
config CRYPTO_SHA256_ARM
|
|
|
|
|
tristate "SHA-224/256 digest algorithm (ARM-asm and NEON)"
|
|
|
|
|
select CRYPTO_HASH
|
2015-04-11 08:48:44 +00:00
|
|
|
depends on !CPU_V7M
|
2015-04-03 10:03:40 +00:00
|
|
|
help
|
|
|
|
|
SHA-256 secure hash standard (DFIPS 180-2) implemented
|
|
|
|
|
using optimized ARM assembler and NEON, when available.
|
|
|
|
|
|
2015-05-08 08:46:21 +00:00
|
|
|
config CRYPTO_SHA512_ARM
|
|
|
|
|
tristate "SHA-384/512 digest algorithm (ARM-asm and NEON)"
|
2015-03-10 08:47:44 +00:00
|
|
|
select CRYPTO_HASH
|
2015-05-08 08:46:21 +00:00
|
|
|
depends on !CPU_V7M
|
2015-03-10 08:47:44 +00:00
|
|
|
help
|
|
|
|
|
SHA-512 secure hash standard (DFIPS 180-2) implemented
|
2015-05-08 08:46:21 +00:00
|
|
|
using optimized ARM assembler and NEON, when available.
|
2015-03-10 08:47:44 +00:00
|
|
|
|
crypto: arm/blake2s - add ARM scalar optimized BLAKE2s
Add an ARM scalar optimized implementation of BLAKE2s.
NEON isn't very useful for BLAKE2s because the BLAKE2s block size is too
small for NEON to help. Each NEON instruction would depend on the
previous one, resulting in poor performance.
With scalar instructions, on the other hand, we can take advantage of
ARM's "free" rotations (like I did in chacha-scalar-core.S) to get an
implementation get runs much faster than the C implementation.
Performance results on Cortex-A7 in cycles per byte using the shash API:
4096-byte messages:
blake2s-256-arm: 18.8
blake2s-256-generic: 26.0
500-byte messages:
blake2s-256-arm: 20.3
blake2s-256-generic: 27.9
100-byte messages:
blake2s-256-arm: 29.7
blake2s-256-generic: 39.2
32-byte messages:
blake2s-256-arm: 50.6
blake2s-256-generic: 66.2
Except on very short messages, this is still slower than the NEON
implementation of BLAKE2b which I've written; that is 14.0, 16.4, 25.8,
and 76.1 cpb on 4096, 500, 100, and 32-byte messages, respectively.
However, optimized BLAKE2s is useful for cases where BLAKE2s is used
instead of BLAKE2b, such as WireGuard.
This new implementation is added in the form of a new module
blake2s-arm.ko, which is analogous to blake2s-x86_64.ko in that it
provides blake2s_compress_arch() for use by the library API as well as
optionally register the algorithms with the shash API.
Acked-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Tested-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2020-12-23 08:09:59 +00:00
|
|
|
config CRYPTO_BLAKE2S_ARM
|
|
|
|
|
tristate "BLAKE2s digest algorithm (ARM)"
|
|
|
|
|
select CRYPTO_ARCH_HAVE_LIB_BLAKE2S
|
|
|
|
|
help
|
|
|
|
|
BLAKE2s digest algorithm optimized with ARM scalar instructions. This
|
|
|
|
|
is faster than the generic implementations of BLAKE2s and BLAKE2b, but
|
|
|
|
|
slower than the NEON implementation of BLAKE2b. (There is no NEON
|
|
|
|
|
implementation of BLAKE2s, since NEON doesn't really help with it.)
|
|
|
|
|
|
crypto: arm/blake2b - add NEON-accelerated BLAKE2b
Add a NEON-accelerated implementation of BLAKE2b.
On Cortex-A7 (which these days is the most common ARM processor that
doesn't have the ARMv8 Crypto Extensions), this is over twice as fast as
SHA-256, and slightly faster than SHA-1. It is also almost three times
as fast as the generic implementation of BLAKE2b:
Algorithm Cycles per byte (on 4096-byte messages)
=================== =======================================
blake2b-256-neon 14.0
sha1-neon 16.3
blake2s-256-arm 18.8
sha1-asm 20.8
blake2s-256-generic 26.0
sha256-neon 28.9
sha256-asm 32.0
blake2b-256-generic 38.9
This implementation isn't directly based on any other implementation,
but it borrows some ideas from previous NEON code I've written as well
as from chacha-neon-core.S. At least on Cortex-A7, it is faster than
the other NEON implementations of BLAKE2b I'm aware of (the
implementation in the BLAKE2 official repository using intrinsics, and
Andrew Moon's implementation which can be found in SUPERCOP). It does
only one block at a time, so it performs well on short messages too.
NEON-accelerated BLAKE2b is useful because there is interest in using
BLAKE2b-256 for dm-verity on low-end Android devices (specifically,
devices that lack the ARMv8 Crypto Extensions) to replace SHA-1. On
these devices, the performance cost of upgrading to SHA-256 may be
unacceptable, whereas BLAKE2b-256 would actually improve performance.
Although BLAKE2b is intended for 64-bit platforms (unlike BLAKE2s which
is intended for 32-bit platforms), on 32-bit ARM processors with NEON,
BLAKE2b is actually faster than BLAKE2s. This is because NEON supports
64-bit operations, and because BLAKE2s's block size is too small for
NEON to be helpful for it. The best I've been able to do with BLAKE2s
on Cortex-A7 is 18.8 cpb with an optimized scalar implementation.
(I didn't try BLAKE2sp and BLAKE3, which in theory would be faster, but
they're more complex as they require running multiple hashes at once.
Note that BLAKE2b already uses all the NEON bandwidth on the Cortex-A7,
so I expect that any speedup from BLAKE2sp or BLAKE3 would come only
from the smaller number of rounds, not from the extra parallelism.)
For now this BLAKE2b implementation is only wired up to the shash API,
since there is no library API for BLAKE2b yet. However, I've tried to
keep things consistent with BLAKE2s, e.g. by defining
blake2b_compress_arch() which is analogous to blake2s_compress_arch()
and could be exported for use by the library API later if needed.
Acked-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Tested-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2020-12-23 08:10:03 +00:00
|
|
|
config CRYPTO_BLAKE2B_NEON
|
|
|
|
|
tristate "BLAKE2b digest algorithm (ARM NEON)"
|
|
|
|
|
depends on KERNEL_MODE_NEON
|
|
|
|
|
select CRYPTO_BLAKE2B
|
|
|
|
|
help
|
|
|
|
|
BLAKE2b digest algorithm optimized with ARM NEON instructions.
|
|
|
|
|
On ARM processors that have NEON support but not the ARMv8
|
|
|
|
|
Crypto Extensions, typically this BLAKE2b implementation is
|
|
|
|
|
much faster than SHA-2 and slightly faster than SHA-1.
|
|
|
|
|
|
2015-03-10 08:47:44 +00:00
|
|
|
config CRYPTO_AES_ARM
|
2017-01-11 16:41:53 +00:00
|
|
|
tristate "Scalar AES cipher for ARM"
|
2015-03-10 08:47:44 +00:00
|
|
|
select CRYPTO_ALGAPI
|
|
|
|
|
select CRYPTO_AES
|
|
|
|
|
help
|
|
|
|
|
Use optimized AES assembler routines for ARM platforms.
|
|
|
|
|
|
2018-10-18 04:37:59 +00:00
|
|
|
On ARM processors without the Crypto Extensions, this is the
|
|
|
|
|
fastest AES implementation for single blocks. For multiple
|
|
|
|
|
blocks, the NEON bit-sliced implementation is usually faster.
|
|
|
|
|
|
|
|
|
|
This implementation may be vulnerable to cache timing attacks,
|
|
|
|
|
since it uses lookup tables. However, as countermeasures it
|
|
|
|
|
disables IRQs and preloads the tables; it is hoped this makes
|
|
|
|
|
such attacks very difficult.
|
|
|
|
|
|
2015-03-10 08:47:44 +00:00
|
|
|
config CRYPTO_AES_ARM_BS
|
|
|
|
|
tristate "Bit sliced AES using NEON instructions"
|
|
|
|
|
depends on KERNEL_MODE_NEON
|
2019-10-25 19:41:13 +00:00
|
|
|
select CRYPTO_SKCIPHER
|
2019-07-02 19:41:29 +00:00
|
|
|
select CRYPTO_LIB_AES
|
2022-03-16 22:55:13 +00:00
|
|
|
select CRYPTO_AES
|
|
|
|
|
select CRYPTO_CBC
|
2016-11-29 08:43:33 +00:00
|
|
|
select CRYPTO_SIMD
|
2015-03-10 08:47:44 +00:00
|
|
|
help
|
|
|
|
|
Use a faster and more secure NEON based implementation of AES in CBC,
|
|
|
|
|
CTR and XTS modes
|
|
|
|
|
|
|
|
|
|
Bit sliced AES gives around 45% speedup on Cortex-A15 for CTR mode
|
|
|
|
|
and for XTS mode encryption, CBC and XTS mode decryption speedup is
|
|
|
|
|
around 25%. (CBC encryption speed is not affected by this driver.)
|
|
|
|
|
This implementation does not rely on any lookup tables so it is
|
|
|
|
|
believed to be invulnerable to cache timing attacks.
|
|
|
|
|
|
2015-03-10 08:47:47 +00:00
|
|
|
config CRYPTO_AES_ARM_CE
|
|
|
|
|
tristate "Accelerated AES using ARMv8 Crypto Extensions"
|
2020-01-22 19:38:21 +00:00
|
|
|
depends on KERNEL_MODE_NEON
|
2019-10-25 19:41:13 +00:00
|
|
|
select CRYPTO_SKCIPHER
|
2019-09-17 08:50:01 +00:00
|
|
|
select CRYPTO_LIB_AES
|
2016-11-29 07:08:40 +00:00
|
|
|
select CRYPTO_SIMD
|
2015-03-10 08:47:47 +00:00
|
|
|
help
|
|
|
|
|
Use an implementation of AES in CBC, CTR and XTS modes that uses
|
|
|
|
|
ARMv8 Crypto Extensions
|
|
|
|
|
|
2015-03-10 08:47:48 +00:00
|
|
|
config CRYPTO_GHASH_ARM_CE
|
2017-07-24 10:28:17 +00:00
|
|
|
tristate "PMULL-accelerated GHASH using NEON/ARMv8 Crypto Extensions"
|
2020-01-22 19:38:21 +00:00
|
|
|
depends on KERNEL_MODE_NEON
|
2015-03-10 08:47:48 +00:00
|
|
|
select CRYPTO_HASH
|
|
|
|
|
select CRYPTO_CRYPTD
|
2018-08-23 14:48:51 +00:00
|
|
|
select CRYPTO_GF128MUL
|
2015-03-10 08:47:48 +00:00
|
|
|
help
|
|
|
|
|
Use an implementation of GHASH (used by the GCM AEAD chaining mode)
|
|
|
|
|
that uses the 64x64 to 128 bit polynomial multiplication (vmull.p64)
|
2017-07-24 10:28:17 +00:00
|
|
|
that is part of the ARMv8 Crypto Extensions, or a slower variant that
|
|
|
|
|
uses the vmull.p8 instruction that is part of the basic NEON ISA.
|
2015-03-10 08:47:48 +00:00
|
|
|
|
2016-12-05 18:42:26 +00:00
|
|
|
config CRYPTO_CRCT10DIF_ARM_CE
|
|
|
|
|
tristate "CRCT10DIF digest algorithm using PMULL instructions"
|
2020-01-22 19:38:21 +00:00
|
|
|
depends on KERNEL_MODE_NEON
|
2019-10-11 09:08:00 +00:00
|
|
|
depends on CRC_T10DIF
|
2016-12-05 18:42:26 +00:00
|
|
|
select CRYPTO_HASH
|
|
|
|
|
|
2016-12-05 18:42:28 +00:00
|
|
|
config CRYPTO_CRC32_ARM_CE
|
|
|
|
|
tristate "CRC32(C) digest algorithm using CRC and/or PMULL instructions"
|
2020-01-22 19:38:21 +00:00
|
|
|
depends on KERNEL_MODE_NEON
|
2019-10-11 09:08:00 +00:00
|
|
|
depends on CRC32
|
2016-12-05 18:42:28 +00:00
|
|
|
select CRYPTO_HASH
|
|
|
|
|
|
2017-01-11 16:41:50 +00:00
|
|
|
config CRYPTO_CHACHA20_NEON
|
2019-11-08 12:22:14 +00:00
|
|
|
tristate "NEON and scalar accelerated ChaCha stream cipher algorithms"
|
2019-10-25 19:41:13 +00:00
|
|
|
select CRYPTO_SKCIPHER
|
2019-11-08 12:22:15 +00:00
|
|
|
select CRYPTO_ARCH_HAVE_LIB_CHACHA
|
2017-01-11 16:41:50 +00:00
|
|
|
|
2019-11-08 12:22:25 +00:00
|
|
|
config CRYPTO_POLY1305_ARM
|
|
|
|
|
tristate "Accelerated scalar and SIMD Poly1305 hash implementations"
|
|
|
|
|
select CRYPTO_HASH
|
|
|
|
|
select CRYPTO_ARCH_HAVE_LIB_POLY1305
|
2017-01-11 16:41:50 +00:00
|
|
|
|
2018-11-17 01:26:30 +00:00
|
|
|
config CRYPTO_NHPOLY1305_NEON
|
|
|
|
|
tristate "NEON accelerated NHPoly1305 hash function (for Adiantum)"
|
|
|
|
|
depends on KERNEL_MODE_NEON
|
|
|
|
|
select CRYPTO_NHPOLY1305
|
|
|
|
|
|
2019-11-08 12:22:38 +00:00
|
|
|
config CRYPTO_CURVE25519_NEON
|
|
|
|
|
tristate "NEON accelerated Curve25519 scalar multiplication library"
|
|
|
|
|
depends on KERNEL_MODE_NEON
|
|
|
|
|
select CRYPTO_LIB_CURVE25519_GENERIC
|
|
|
|
|
select CRYPTO_ARCH_HAVE_LIB_CURVE25519
|
|
|
|
|
|
2015-03-10 08:47:44 +00:00
|
|
|
endif
|