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
|
2014-07-22 09:20:12 +00:00
|
|
|
config HAVE_ACPI_APEI
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config HAVE_ACPI_APEI_NMI
|
|
|
|
|
bool
|
|
|
|
|
|
2010-05-18 06:35:12 +00:00
|
|
|
config ACPI_APEI
|
|
|
|
|
bool "ACPI Platform Error Interface (APEI)"
|
2011-04-13 17:48:12 +00:00
|
|
|
select MISC_FILESYSTEMS
|
2011-01-03 22:22:11 +00:00
|
|
|
select PSTORE
|
2013-10-28 21:06:55 +00:00
|
|
|
select UEFI_CPER
|
2014-07-22 09:20:12 +00:00
|
|
|
depends on HAVE_ACPI_APEI
|
2010-05-18 06:35:12 +00:00
|
|
|
help
|
|
|
|
|
APEI allows to report errors (for example from the chipset)
|
|
|
|
|
to the operating system. This improves NMI handling
|
|
|
|
|
especially. In addition it supports error serialization and
|
|
|
|
|
error injection.
|
2010-05-18 06:35:14 +00:00
|
|
|
|
ACPI, APEI, Generic Hardware Error Source memory error support
Generic Hardware Error Source provides a way to report platform
hardware errors (such as that from chipset). It works in so called
"Firmware First" mode, that is, hardware errors are reported to
firmware firstly, then reported to Linux by firmware. This way, some
non-standard hardware error registers or non-standard hardware link
can be checked by firmware to produce more valuable hardware error
information for Linux.
Now, only SCI notification type and memory errors are supported. More
notification type and hardware error type will be added later. These
memory errors are reported to user space through /dev/mcelog via
faking a corrected Machine Check, so that the error memory page can be
offlined by /sbin/mcelog if the error count for one page is beyond the
threshold.
On some machines, Machine Check can not report physical address for
some corrected memory errors, but GHES can do that. So this simplified
GHES is implemented firstly.
Signed-off-by: Huang Ying <ying.huang@intel.com>
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2010-05-18 06:35:20 +00:00
|
|
|
config ACPI_APEI_GHES
|
2011-07-13 05:14:18 +00:00
|
|
|
bool "APEI Generic Hardware Error Source"
|
2014-02-10 16:23:36 +00:00
|
|
|
depends on ACPI_APEI
|
ACPI, APEI, Generic Hardware Error Source memory error support
Generic Hardware Error Source provides a way to report platform
hardware errors (such as that from chipset). It works in so called
"Firmware First" mode, that is, hardware errors are reported to
firmware firstly, then reported to Linux by firmware. This way, some
non-standard hardware error registers or non-standard hardware link
can be checked by firmware to produce more valuable hardware error
information for Linux.
Now, only SCI notification type and memory errors are supported. More
notification type and hardware error type will be added later. These
memory errors are reported to user space through /dev/mcelog via
faking a corrected Machine Check, so that the error memory page can be
offlined by /sbin/mcelog if the error count for one page is beyond the
threshold.
On some machines, Machine Check can not report physical address for
some corrected memory errors, but GHES can do that. So this simplified
GHES is implemented firstly.
Signed-off-by: Huang Ying <ying.huang@intel.com>
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2010-05-18 06:35:20 +00:00
|
|
|
select ACPI_HED
|
2011-08-10 02:46:22 +00:00
|
|
|
select IRQ_WORK
|
ACPI, APEI, GHES, printk support for recoverable error via NMI
Some APEI GHES recoverable errors are reported via NMI, but printk is
not safe in NMI context.
To solve the issue, a lock-less memory allocator is used to allocate
memory in NMI handler, save the error record into the allocated
memory, put the error record into a lock-less list. On the other
hand, an irq_work is used to delay the operation from NMI context to
IRQ context. The irq_work IRQ handler will remove nodes from
lock-less list, printk the error record and do some further processing
include recovery operation, then free the memory.
Signed-off-by: Huang Ying <ying.huang@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2011-07-13 05:14:25 +00:00
|
|
|
select GENERIC_ALLOCATOR
|
ACPI, APEI, Generic Hardware Error Source memory error support
Generic Hardware Error Source provides a way to report platform
hardware errors (such as that from chipset). It works in so called
"Firmware First" mode, that is, hardware errors are reported to
firmware firstly, then reported to Linux by firmware. This way, some
non-standard hardware error registers or non-standard hardware link
can be checked by firmware to produce more valuable hardware error
information for Linux.
Now, only SCI notification type and memory errors are supported. More
notification type and hardware error type will be added later. These
memory errors are reported to user space through /dev/mcelog via
faking a corrected Machine Check, so that the error memory page can be
offlined by /sbin/mcelog if the error count for one page is beyond the
threshold.
On some machines, Machine Check can not report physical address for
some corrected memory errors, but GHES can do that. So this simplified
GHES is implemented firstly.
Signed-off-by: Huang Ying <ying.huang@intel.com>
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
2010-05-18 06:35:20 +00:00
|
|
|
help
|
|
|
|
|
Generic Hardware Error Source provides a way to report
|
|
|
|
|
platform hardware errors (such as that from chipset). It
|
|
|
|
|
works in so called "Firmware First" mode, that is, hardware
|
|
|
|
|
errors are reported to firmware firstly, then reported to
|
|
|
|
|
Linux by firmware. This way, some non-standard hardware
|
|
|
|
|
error registers or non-standard hardware link can be checked
|
|
|
|
|
by firmware to produce more valuable hardware error
|
|
|
|
|
information for Linux.
|
|
|
|
|
|
2011-02-21 05:54:43 +00:00
|
|
|
config ACPI_APEI_PCIEAER
|
|
|
|
|
bool "APEI PCIe AER logging/recovering support"
|
|
|
|
|
depends on ACPI_APEI && PCIEAER
|
|
|
|
|
help
|
|
|
|
|
PCIe AER errors may be reported via APEI firmware first mode.
|
|
|
|
|
Turn on this option to enable the corresponding support.
|
|
|
|
|
|
2017-06-21 18:17:09 +00:00
|
|
|
config ACPI_APEI_SEA
|
2019-01-29 18:48:48 +00:00
|
|
|
bool
|
2017-06-21 18:17:09 +00:00
|
|
|
depends on ARM64 && ACPI_APEI_GHES
|
|
|
|
|
default y
|
|
|
|
|
|
2011-07-13 05:14:28 +00:00
|
|
|
config ACPI_APEI_MEMORY_FAILURE
|
|
|
|
|
bool "APEI memory error recovering support"
|
|
|
|
|
depends on ACPI_APEI && MEMORY_FAILURE
|
|
|
|
|
help
|
|
|
|
|
Memory errors may be reported via APEI firmware first mode.
|
|
|
|
|
Turn on this option to enable the memory recovering support.
|
|
|
|
|
|
2010-05-18 06:35:14 +00:00
|
|
|
config ACPI_APEI_EINJ
|
|
|
|
|
tristate "APEI Error INJection (EINJ)"
|
|
|
|
|
depends on ACPI_APEI && DEBUG_FS
|
|
|
|
|
help
|
|
|
|
|
EINJ provides a hardware error injection mechanism, it is
|
|
|
|
|
mainly used for debugging and testing the other parts of
|
|
|
|
|
APEI and some other RAS features.
|
2010-08-12 03:55:17 +00:00
|
|
|
|
|
|
|
|
config ACPI_APEI_ERST_DEBUG
|
|
|
|
|
tristate "APEI Error Record Serialization Table (ERST) Debug Support"
|
|
|
|
|
depends on ACPI_APEI
|
|
|
|
|
help
|
|
|
|
|
ERST is a way provided by APEI to save and retrieve hardware
|
2010-09-07 16:49:45 +00:00
|
|
|
error information to and from a persistent store. Enable this
|
2010-08-12 03:55:17 +00:00
|
|
|
if you want to debugging and testing the ERST kernel support
|
|
|
|
|
and firmware implementation.
|