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 */
|
2009-04-10 21:36:00 +08:00
|
|
|
/*
|
2012-09-02 01:31:09 +08:00
|
|
|
* Trace files that want to automate creation of all tracepoints defined
|
2009-04-10 21:36:00 +08:00
|
|
|
* in their file should include this file. The following are macros that the
|
|
|
|
|
* trace file may define:
|
|
|
|
|
*
|
|
|
|
|
* TRACE_SYSTEM defines the system the tracepoint is for
|
|
|
|
|
*
|
|
|
|
|
* TRACE_INCLUDE_FILE if the file name is something other than TRACE_SYSTEM.h
|
|
|
|
|
* This macro may be defined to tell define_trace.h what file to include.
|
|
|
|
|
* Note, leave off the ".h".
|
|
|
|
|
*
|
|
|
|
|
* TRACE_INCLUDE_PATH if the path is something other than core kernel include/trace
|
|
|
|
|
* then this macro can define the path to use. Note, the path is relative to
|
|
|
|
|
* define_trace.h, not the file including it. Full path names for out of tree
|
|
|
|
|
* modules must be used.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifdef CREATE_TRACE_POINTS
|
|
|
|
|
|
|
|
|
|
/* Prevent recursion */
|
|
|
|
|
#undef CREATE_TRACE_POINTS
|
|
|
|
|
|
|
|
|
|
#include <linux/stringify.h>
|
|
|
|
|
|
|
|
|
|
#undef TRACE_EVENT
|
|
|
|
|
#define TRACE_EVENT(name, proto, args, tstruct, assign, print) \
|
2020-08-18 21:57:52 +08:00
|
|
|
DEFINE_TRACE(name, PARAMS(proto), PARAMS(args))
|
2009-04-10 21:36:00 +08:00
|
|
|
|
2010-12-03 05:46:18 +08:00
|
|
|
#undef TRACE_EVENT_CONDITION
|
|
|
|
|
#define TRACE_EVENT_CONDITION(name, proto, args, cond, tstruct, assign, print) \
|
|
|
|
|
TRACE_EVENT(name, \
|
|
|
|
|
PARAMS(proto), \
|
|
|
|
|
PARAMS(args), \
|
|
|
|
|
PARAMS(tstruct), \
|
|
|
|
|
PARAMS(assign), \
|
|
|
|
|
PARAMS(print))
|
|
|
|
|
|
2009-08-25 05:43:13 +08:00
|
|
|
#undef TRACE_EVENT_FN
|
|
|
|
|
#define TRACE_EVENT_FN(name, proto, args, tstruct, \
|
|
|
|
|
assign, print, reg, unreg) \
|
2020-08-18 21:57:52 +08:00
|
|
|
DEFINE_TRACE_FN(name, reg, unreg, PARAMS(proto), PARAMS(args))
|
2009-08-25 05:43:13 +08:00
|
|
|
|
2015-12-15 04:18:05 +08:00
|
|
|
#undef TRACE_EVENT_FN_COND
|
|
|
|
|
#define TRACE_EVENT_FN_COND(name, proto, args, cond, tstruct, \
|
|
|
|
|
assign, print, reg, unreg) \
|
2020-08-18 21:57:52 +08:00
|
|
|
DEFINE_TRACE_FN(name, reg, unreg, PARAMS(proto), PARAMS(args))
|
2015-12-15 04:18:05 +08:00
|
|
|
|
2019-03-26 20:13:09 +08:00
|
|
|
#undef TRACE_EVENT_NOP
|
|
|
|
|
#define TRACE_EVENT_NOP(name, proto, args, struct, assign, print)
|
|
|
|
|
|
|
|
|
|
#undef DEFINE_EVENT_NOP
|
|
|
|
|
#define DEFINE_EVENT_NOP(template, name, proto, args)
|
|
|
|
|
|
tracing: Create new TRACE_EVENT_TEMPLATE
There are some places in the kernel that define several tracepoints and
they are all identical besides the name. The code to enable, disable and
record is created for every trace point even if most of the code is
identical.
This patch adds TRACE_EVENT_TEMPLATE that lets the developer create
a template TRACE_EVENT and create trace points with DEFINE_EVENT, which
is based off of a given template. Each trace point used by this
will share most of the code, and bring down the size of the kernel
when there are several duplicate events.
Usage is:
TRACE_EVENT_TEMPLATE(name, proto, args, tstruct, assign, print);
Which would be the same as defining a normal TRACE_EVENT.
To create the trace events that the trace points will use:
DEFINE_EVENT(template, name, proto, args) is done. The template
is the name of the TRACE_EVENT_TEMPLATE to use. The name is the
name of the trace point. The parameters proto and args must be the same
as the proto and args of the template. If they are not the same,
then a compile error will result. I tried hard removing this duplication
but the C preprocessor is not powerful enough (or my CPP magic
experience points is not at a high enough level) to not need them.
A lot of trace events are coming in with new XFS development. Most of
the trace points are identical except for the name. The following shows
the advantage of having TRACE_EVENT_TEMPLATE:
$ size fs/xfs/xfs.o.*
text data bss dec hex filename
452114 2788 3520 458422 6feb6 fs/xfs/xfs.o.old
638482 38116 3744 680342 a6196 fs/xfs/xfs.o.template
996954 38116 4480 1039550 fdcbe fs/xfs/xfs.o.trace
xfs.o.old is without any tracepoints.
xfs.o.template uses the new TRACE_EVENT_TEMPLATE.
xfs.o.trace uses the current TRACE_EVENT macros.
Requested-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2009-11-19 09:27:27 +08:00
|
|
|
#undef DEFINE_EVENT
|
|
|
|
|
#define DEFINE_EVENT(template, name, proto, args) \
|
2020-08-18 21:57:52 +08:00
|
|
|
DEFINE_TRACE(name, PARAMS(proto), PARAMS(args))
|
tracing: Create new TRACE_EVENT_TEMPLATE
There are some places in the kernel that define several tracepoints and
they are all identical besides the name. The code to enable, disable and
record is created for every trace point even if most of the code is
identical.
This patch adds TRACE_EVENT_TEMPLATE that lets the developer create
a template TRACE_EVENT and create trace points with DEFINE_EVENT, which
is based off of a given template. Each trace point used by this
will share most of the code, and bring down the size of the kernel
when there are several duplicate events.
Usage is:
TRACE_EVENT_TEMPLATE(name, proto, args, tstruct, assign, print);
Which would be the same as defining a normal TRACE_EVENT.
To create the trace events that the trace points will use:
DEFINE_EVENT(template, name, proto, args) is done. The template
is the name of the TRACE_EVENT_TEMPLATE to use. The name is the
name of the trace point. The parameters proto and args must be the same
as the proto and args of the template. If they are not the same,
then a compile error will result. I tried hard removing this duplication
but the C preprocessor is not powerful enough (or my CPP magic
experience points is not at a high enough level) to not need them.
A lot of trace events are coming in with new XFS development. Most of
the trace points are identical except for the name. The following shows
the advantage of having TRACE_EVENT_TEMPLATE:
$ size fs/xfs/xfs.o.*
text data bss dec hex filename
452114 2788 3520 458422 6feb6 fs/xfs/xfs.o.old
638482 38116 3744 680342 a6196 fs/xfs/xfs.o.template
996954 38116 4480 1039550 fdcbe fs/xfs/xfs.o.trace
xfs.o.old is without any tracepoints.
xfs.o.template uses the new TRACE_EVENT_TEMPLATE.
xfs.o.trace uses the current TRACE_EVENT macros.
Requested-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2009-11-19 09:27:27 +08:00
|
|
|
|
2013-06-20 23:44:44 +08:00
|
|
|
#undef DEFINE_EVENT_FN
|
|
|
|
|
#define DEFINE_EVENT_FN(template, name, proto, args, reg, unreg) \
|
2020-08-18 21:57:52 +08:00
|
|
|
DEFINE_TRACE_FN(name, reg, unreg, PARAMS(proto), PARAMS(args))
|
2013-06-20 23:44:44 +08:00
|
|
|
|
2009-11-19 09:36:26 +08:00
|
|
|
#undef DEFINE_EVENT_PRINT
|
|
|
|
|
#define DEFINE_EVENT_PRINT(template, name, proto, args, print) \
|
2020-08-18 21:57:52 +08:00
|
|
|
DEFINE_TRACE(name, PARAMS(proto), PARAMS(args))
|
2009-11-19 09:36:26 +08:00
|
|
|
|
2010-12-03 05:46:18 +08:00
|
|
|
#undef DEFINE_EVENT_CONDITION
|
|
|
|
|
#define DEFINE_EVENT_CONDITION(template, name, proto, args, cond) \
|
|
|
|
|
DEFINE_EVENT(template, name, PARAMS(proto), PARAMS(args))
|
|
|
|
|
|
2009-04-10 21:36:00 +08:00
|
|
|
#undef DECLARE_TRACE
|
|
|
|
|
#define DECLARE_TRACE(name, proto, args) \
|
2020-08-18 21:57:52 +08:00
|
|
|
DEFINE_TRACE(name, PARAMS(proto), PARAMS(args))
|
2009-04-10 21:36:00 +08:00
|
|
|
|
|
|
|
|
#undef TRACE_INCLUDE
|
|
|
|
|
#undef __TRACE_INCLUDE
|
|
|
|
|
|
|
|
|
|
#ifndef TRACE_INCLUDE_FILE
|
|
|
|
|
# define TRACE_INCLUDE_FILE TRACE_SYSTEM
|
|
|
|
|
# define UNDEF_TRACE_INCLUDE_FILE
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifndef TRACE_INCLUDE_PATH
|
2009-04-15 07:39:12 +08:00
|
|
|
# define __TRACE_INCLUDE(system) <trace/events/system.h>
|
2009-04-24 11:26:18 +08:00
|
|
|
# define UNDEF_TRACE_INCLUDE_PATH
|
2009-04-10 21:36:00 +08:00
|
|
|
#else
|
|
|
|
|
# define __TRACE_INCLUDE(system) __stringify(TRACE_INCLUDE_PATH/system.h)
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
# define TRACE_INCLUDE(system) __TRACE_INCLUDE(system)
|
|
|
|
|
|
|
|
|
|
/* Let the trace headers be reread */
|
|
|
|
|
#define TRACE_HEADER_MULTI_READ
|
|
|
|
|
|
|
|
|
|
#include TRACE_INCLUDE(TRACE_INCLUDE_FILE)
|
|
|
|
|
|
2010-05-05 22:52:31 +08:00
|
|
|
/* Make all open coded DECLARE_TRACE nops */
|
|
|
|
|
#undef DECLARE_TRACE
|
|
|
|
|
#define DECLARE_TRACE(name, proto, args)
|
|
|
|
|
|
2015-08-01 20:27:57 +08:00
|
|
|
#ifdef TRACEPOINTS_ENABLED
|
2015-04-29 21:57:36 +08:00
|
|
|
#include <trace/trace_events.h>
|
2015-04-30 01:11:00 +08:00
|
|
|
#include <trace/perf.h>
|
2018-03-29 03:05:37 +08:00
|
|
|
#include <trace/bpf_probe.h>
|
2009-04-14 00:25:37 +08:00
|
|
|
#endif
|
|
|
|
|
|
2009-08-25 14:06:22 +08:00
|
|
|
#undef TRACE_EVENT
|
2009-08-28 00:17:34 +08:00
|
|
|
#undef TRACE_EVENT_FN
|
2015-12-15 04:18:05 +08:00
|
|
|
#undef TRACE_EVENT_FN_COND
|
2010-12-03 05:46:18 +08:00
|
|
|
#undef TRACE_EVENT_CONDITION
|
2019-03-26 20:13:09 +08:00
|
|
|
#undef TRACE_EVENT_NOP
|
|
|
|
|
#undef DEFINE_EVENT_NOP
|
2009-11-26 16:04:55 +08:00
|
|
|
#undef DECLARE_EVENT_CLASS
|
tracing: Create new TRACE_EVENT_TEMPLATE
There are some places in the kernel that define several tracepoints and
they are all identical besides the name. The code to enable, disable and
record is created for every trace point even if most of the code is
identical.
This patch adds TRACE_EVENT_TEMPLATE that lets the developer create
a template TRACE_EVENT and create trace points with DEFINE_EVENT, which
is based off of a given template. Each trace point used by this
will share most of the code, and bring down the size of the kernel
when there are several duplicate events.
Usage is:
TRACE_EVENT_TEMPLATE(name, proto, args, tstruct, assign, print);
Which would be the same as defining a normal TRACE_EVENT.
To create the trace events that the trace points will use:
DEFINE_EVENT(template, name, proto, args) is done. The template
is the name of the TRACE_EVENT_TEMPLATE to use. The name is the
name of the trace point. The parameters proto and args must be the same
as the proto and args of the template. If they are not the same,
then a compile error will result. I tried hard removing this duplication
but the C preprocessor is not powerful enough (or my CPP magic
experience points is not at a high enough level) to not need them.
A lot of trace events are coming in with new XFS development. Most of
the trace points are identical except for the name. The following shows
the advantage of having TRACE_EVENT_TEMPLATE:
$ size fs/xfs/xfs.o.*
text data bss dec hex filename
452114 2788 3520 458422 6feb6 fs/xfs/xfs.o.old
638482 38116 3744 680342 a6196 fs/xfs/xfs.o.template
996954 38116 4480 1039550 fdcbe fs/xfs/xfs.o.trace
xfs.o.old is without any tracepoints.
xfs.o.template uses the new TRACE_EVENT_TEMPLATE.
xfs.o.trace uses the current TRACE_EVENT macros.
Requested-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2009-11-19 09:27:27 +08:00
|
|
|
#undef DEFINE_EVENT
|
2013-06-20 23:44:44 +08:00
|
|
|
#undef DEFINE_EVENT_FN
|
2009-11-19 09:36:26 +08:00
|
|
|
#undef DEFINE_EVENT_PRINT
|
2010-12-03 05:46:18 +08:00
|
|
|
#undef DEFINE_EVENT_CONDITION
|
2009-04-10 21:36:00 +08:00
|
|
|
#undef TRACE_HEADER_MULTI_READ
|
2010-05-05 22:52:31 +08:00
|
|
|
#undef DECLARE_TRACE
|
2009-04-10 21:36:00 +08:00
|
|
|
|
|
|
|
|
/* Only undef what we defined in this file */
|
|
|
|
|
#ifdef UNDEF_TRACE_INCLUDE_FILE
|
2009-04-24 11:26:18 +08:00
|
|
|
# undef TRACE_INCLUDE_FILE
|
2009-04-10 21:36:00 +08:00
|
|
|
# undef UNDEF_TRACE_INCLUDE_FILE
|
|
|
|
|
#endif
|
|
|
|
|
|
2009-04-24 11:26:18 +08:00
|
|
|
#ifdef UNDEF_TRACE_INCLUDE_PATH
|
2009-04-10 21:36:00 +08:00
|
|
|
# undef TRACE_INCLUDE_PATH
|
2009-04-24 11:26:18 +08:00
|
|
|
# undef UNDEF_TRACE_INCLUDE_PATH
|
2009-04-10 21:36:00 +08:00
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
/* We may be processing more files */
|
|
|
|
|
#define CREATE_TRACE_POINTS
|
|
|
|
|
|
|
|
|
|
#endif /* CREATE_TRACE_POINTS */
|
