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 22:07:57 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2005-04-17 06:20:36 +08:00
|
|
|
config STATIC_LINK
|
|
|
|
|
bool "Force a static link"
|
|
|
|
|
default n
|
|
|
|
|
help
|
2007-10-16 16:26:54 +08:00
|
|
|
This option gives you the ability to force a static link of UML.
|
|
|
|
|
Normally, UML is linked as a shared binary. This is inconvenient for
|
|
|
|
|
use in a chroot jail. So, if you intend to run UML inside a chroot,
|
|
|
|
|
you probably want to say Y here.
|
|
|
|
|
Additionally, this option enables using higher memory spaces (up to
|
|
|
|
|
2.75G) for UML.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2005-06-23 15:07:43 +08:00
|
|
|
source "mm/Kconfig"
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config LD_SCRIPT_STATIC
|
|
|
|
|
bool
|
|
|
|
|
default y
|
uml: throw out CONFIG_MODE_TT
This patchset throws out tt mode, which has been non-functional for a while.
This is done in phases, interspersed with code cleanups on the affected files.
The removal is done as follows:
remove all code, config options, and files which depend on
CONFIG_MODE_TT
get rid of the CHOOSE_MODE macro, which decided whether to
call tt-mode or skas-mode code, and replace invocations with their
skas portions
replace all now-trivial procedures with their skas equivalents
There are now a bunch of now-redundant pieces of data structures, including
mode-specific pieces of the thread structure, pt_regs, and mm_context. These
are all replaced with their skas-specific contents.
As part of the ongoing style compliance project, I made a style pass over all
files that were changed. There are three such patches, one for each phase,
covering the files affected by that phase but no later ones.
I noticed that we weren't freeing the LDT state associated with a process when
it exited, so that's fixed in one of the later patches.
The last patch is a tidying patch which I've had for a while, but which caused
inexplicable crashes under tt mode. Since that is no longer a problem, this
can now go in.
This patch:
Start getting rid of tt mode support.
This patch throws out CONFIG_MODE_TT and all config options, code, and files
which depend on it.
CONFIG_MODE_SKAS is gone and everything that depends on it is included
unconditionally.
The few changed lines are in re-written Kconfig help, lines which needed
something skas-related removed from them, and a few more which weren't
strictly deletions.
Signed-off-by: Jeff Dike <jdike@linux.intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2007-10-16 16:26:50 +08:00
|
|
|
depends on STATIC_LINK
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config LD_SCRIPT_DYN
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
depends on !LD_SCRIPT_STATIC
|
2017-08-20 19:26:05 +08:00
|
|
|
select MODULE_REL_CRCS if MODVERSIONS
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
source "fs/Kconfig.binfmt"
|
|
|
|
|
|
|
|
|
|
config HOSTFS
|
|
|
|
|
tristate "Host filesystem"
|
|
|
|
|
help
|
2007-10-16 16:26:54 +08:00
|
|
|
While the User-Mode Linux port uses its own root file system for
|
|
|
|
|
booting and normal file access, this module lets the UML user
|
|
|
|
|
access files stored on the host. It does not require any
|
|
|
|
|
network connection between the Host and UML. An example use of
|
|
|
|
|
this might be:
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-10-16 16:26:54 +08:00
|
|
|
mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-10-16 16:26:54 +08:00
|
|
|
where /tmp/fromhost is an empty directory inside UML and
|
|
|
|
|
/tmp/umlshare is a directory on the host with files the UML user
|
|
|
|
|
wishes to access.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-10-16 16:26:54 +08:00
|
|
|
For more information, see
|
|
|
|
|
<http://user-mode-linux.sourceforge.net/hostfs.html>.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-10-16 16:26:54 +08:00
|
|
|
If you'd like to be able to work with files stored on the host,
|
|
|
|
|
say Y or M here; otherwise say N.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config MCONSOLE
|
|
|
|
|
bool "Management console"
|
2015-06-01 05:27:26 +08:00
|
|
|
depends on PROC_FS
|
2005-04-17 06:20:36 +08:00
|
|
|
default y
|
|
|
|
|
help
|
2007-10-16 16:26:54 +08:00
|
|
|
The user mode linux management console is a low-level interface to
|
|
|
|
|
the kernel, somewhat like the i386 SysRq interface. Since there is
|
|
|
|
|
a full-blown operating system running under every user mode linux
|
|
|
|
|
instance, there is much greater flexibility possible than with the
|
|
|
|
|
SysRq mechanism.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-10-16 16:26:54 +08:00
|
|
|
If you answer 'Y' to this option, to use this feature, you need the
|
|
|
|
|
mconsole client (called uml_mconsole) which is present in CVS in
|
|
|
|
|
2.4.5-9um and later (path /tools/mconsole), and is also in the
|
|
|
|
|
distribution RPM package in 2.4.6 and later.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-10-16 16:26:54 +08:00
|
|
|
It is safe to say 'Y' here.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config MAGIC_SYSRQ
|
|
|
|
|
bool "Magic SysRq key"
|
|
|
|
|
depends on MCONSOLE
|
2007-10-16 16:26:54 +08:00
|
|
|
help
|
|
|
|
|
If you say Y here, you will have some control over the system even
|
|
|
|
|
if the system crashes for example during kernel debugging (e.g., you
|
|
|
|
|
will be able to flush the buffer cache to disk, reboot the system
|
|
|
|
|
immediately or dump some status information). A key for each of the
|
|
|
|
|
possible requests is provided.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-10-16 16:26:54 +08:00
|
|
|
This is the feature normally accomplished by pressing a key
|
|
|
|
|
while holding SysRq (Alt+PrintScreen).
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2007-10-16 16:26:54 +08:00
|
|
|
On UML, this is accomplished by sending a "sysrq" command with
|
|
|
|
|
mconsole, followed by the letter for the requested command.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2018-05-09 02:14:57 +08:00
|
|
|
The keys are documented in <file:Documentation/admin-guide/sysrq.rst>. Don't say Y
|
2007-10-16 16:26:54 +08:00
|
|
|
unless you really know what this hack does.
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
config KERNEL_STACK_ORDER
|
|
|
|
|
int "Kernel stack size order"
|
2007-05-11 13:22:35 +08:00
|
|
|
default 1 if 64BIT
|
2007-06-09 04:46:49 +08:00
|
|
|
range 1 10 if 64BIT
|
2007-05-11 13:22:35 +08:00
|
|
|
default 0 if !64BIT
|
2005-04-17 06:20:36 +08:00
|
|
|
help
|
2007-10-16 16:26:54 +08:00
|
|
|
This option determines the size of UML kernel stacks. They will
|
|
|
|
|
be 1 << order pages. The default is OK unless you're running Valgrind
|
|
|
|
|
on UML, in which case, set this to 3.
|
2010-10-27 05:22:18 +08:00
|
|
|
|
2011-08-19 03:13:00 +08:00
|
|
|
config MMAPPER
|
|
|
|
|
tristate "iomem emulation driver"
|
|
|
|
|
help
|
|
|
|
|
This driver allows a host file to be used as emulated IO memory inside
|
|
|
|
|
UML.
|
|
|
|
|
|
2010-10-27 05:22:18 +08:00
|
|
|
config NO_DMA
|
|
|
|
|
def_bool y
|
2015-04-15 06:46:11 +08:00
|
|
|
|
|
|
|
|
config PGTABLE_LEVELS
|
|
|
|
|
int
|
|
|
|
|
default 3 if 3_LEVEL_PGTABLES
|
|
|
|
|
default 2
|
2015-12-30 04:35:47 +08:00
|
|
|
|
|
|
|
|
config SECCOMP
|
|
|
|
|
def_bool y
|
|
|
|
|
prompt "Enable seccomp to safely compute untrusted bytecode"
|
|
|
|
|
---help---
|
|
|
|
|
This kernel feature is useful for number crunching applications
|
|
|
|
|
that may need to compute untrusted bytecode during their
|
|
|
|
|
execution. By using pipes or other transports made available to
|
|
|
|
|
the process as file descriptors supporting the read/write
|
|
|
|
|
syscalls, it's possible to isolate those applications in
|
|
|
|
|
their own address space using seccomp. Once seccomp is
|
|
|
|
|
enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
|
|
|
|
|
and the task is only allowed to execute a few safe syscalls
|
|
|
|
|
defined by each seccomp mode.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
