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 21:07:57 +07:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
2010-08-05 21:22:23 +07:00
|
|
|
/*
|
|
|
|
* kdb helper for dumping the ftrace buffer
|
|
|
|
*
|
|
|
|
* Copyright (C) 2010 Jason Wessel <jason.wessel@windriver.com>
|
|
|
|
*
|
|
|
|
* ftrace_dump_buf based on ftrace_dump:
|
|
|
|
* Copyright (C) 2007-2008 Steven Rostedt <srostedt@redhat.com>
|
|
|
|
* Copyright (C) 2008 Ingo Molnar <mingo@redhat.com>
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/kgdb.h>
|
|
|
|
#include <linux/kdb.h>
|
|
|
|
#include <linux/ftrace.h>
|
|
|
|
|
|
|
|
#include "trace.h"
|
|
|
|
#include "trace_output.h"
|
|
|
|
|
2010-08-05 21:22:23 +07:00
|
|
|
static void ftrace_dump_buf(int skip_lines, long cpu_file)
|
2010-08-05 21:22:23 +07:00
|
|
|
{
|
|
|
|
/* use static because iter can be a bit big for the stack */
|
|
|
|
static struct trace_iterator iter;
|
2014-11-06 19:41:55 +07:00
|
|
|
static struct ring_buffer_iter *buffer_iter[CONFIG_NR_CPUS];
|
2015-09-30 20:42:05 +07:00
|
|
|
struct trace_array *tr;
|
2010-08-05 21:22:23 +07:00
|
|
|
unsigned int old_userobj;
|
|
|
|
int cnt = 0, cpu;
|
|
|
|
|
|
|
|
trace_init_global_iter(&iter);
|
2014-11-06 19:41:55 +07:00
|
|
|
iter.buffer_iter = buffer_iter;
|
2015-09-30 20:42:05 +07:00
|
|
|
tr = iter.tr;
|
2010-08-05 21:22:23 +07:00
|
|
|
|
|
|
|
for_each_tracing_cpu(cpu) {
|
tracing: Consolidate max_tr into main trace_array structure
Currently, the way the latency tracers and snapshot feature works
is to have a separate trace_array called "max_tr" that holds the
snapshot buffer. For latency tracers, this snapshot buffer is used
to swap the running buffer with this buffer to save the current max
latency.
The only items needed for the max_tr is really just a copy of the buffer
itself, the per_cpu data pointers, the time_start timestamp that states
when the max latency was triggered, and the cpu that the max latency
was triggered on. All other fields in trace_array are unused by the
max_tr, making the max_tr mostly bloat.
This change removes the max_tr completely, and adds a new structure
called trace_buffer, that holds the buffer pointer, the per_cpu data
pointers, the time_start timestamp, and the cpu where the latency occurred.
The trace_array, now has two trace_buffers, one for the normal trace and
one for the max trace or snapshot. By doing this, not only do we remove
the bloat from the max_trace but the instances of traces can now use
their own snapshot feature and not have just the top level global_trace have
the snapshot feature and latency tracers for itself.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2013-03-05 21:24:35 +07:00
|
|
|
atomic_inc(&per_cpu_ptr(iter.trace_buffer->data, cpu)->disabled);
|
2010-08-05 21:22:23 +07:00
|
|
|
}
|
|
|
|
|
2015-09-30 20:42:05 +07:00
|
|
|
old_userobj = tr->trace_flags;
|
2010-08-05 21:22:23 +07:00
|
|
|
|
|
|
|
/* don't look at user memory in panic mode */
|
2015-09-30 20:42:05 +07:00
|
|
|
tr->trace_flags &= ~TRACE_ITER_SYM_USEROBJ;
|
2010-08-05 21:22:23 +07:00
|
|
|
|
|
|
|
kdb_printf("Dumping ftrace buffer:\n");
|
|
|
|
|
|
|
|
/* reset all but tr, trace, and overruns */
|
|
|
|
memset(&iter.seq, 0,
|
|
|
|
sizeof(struct trace_iterator) -
|
|
|
|
offsetof(struct trace_iterator, seq));
|
|
|
|
iter.iter_flags |= TRACE_FILE_LAT_FMT;
|
|
|
|
iter.pos = -1;
|
|
|
|
|
2013-01-24 03:22:59 +07:00
|
|
|
if (cpu_file == RING_BUFFER_ALL_CPUS) {
|
2010-08-05 21:22:23 +07:00
|
|
|
for_each_tracing_cpu(cpu) {
|
|
|
|
iter.buffer_iter[cpu] =
|
2019-03-09 02:32:04 +07:00
|
|
|
ring_buffer_read_prepare(iter.trace_buffer->buffer,
|
|
|
|
cpu, GFP_ATOMIC);
|
2010-08-05 21:22:23 +07:00
|
|
|
ring_buffer_read_start(iter.buffer_iter[cpu]);
|
|
|
|
tracing_iter_reset(&iter, cpu);
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
iter.cpu_file = cpu_file;
|
|
|
|
iter.buffer_iter[cpu_file] =
|
2019-03-09 02:32:04 +07:00
|
|
|
ring_buffer_read_prepare(iter.trace_buffer->buffer,
|
|
|
|
cpu_file, GFP_ATOMIC);
|
2010-08-05 21:22:23 +07:00
|
|
|
ring_buffer_read_start(iter.buffer_iter[cpu_file]);
|
|
|
|
tracing_iter_reset(&iter, cpu_file);
|
2010-08-05 21:22:23 +07:00
|
|
|
}
|
2014-11-06 19:41:56 +07:00
|
|
|
|
|
|
|
while (trace_find_next_entry_inc(&iter)) {
|
2010-08-05 21:22:23 +07:00
|
|
|
if (!cnt)
|
|
|
|
kdb_printf("---------------------------------\n");
|
|
|
|
cnt++;
|
|
|
|
|
2014-11-06 19:41:56 +07:00
|
|
|
if (!skip_lines) {
|
2010-08-05 21:22:23 +07:00
|
|
|
print_trace_line(&iter);
|
|
|
|
trace_printk_seq(&iter.seq);
|
2014-11-06 19:41:56 +07:00
|
|
|
} else {
|
2010-08-05 21:22:23 +07:00
|
|
|
skip_lines--;
|
2014-11-06 19:41:56 +07:00
|
|
|
}
|
|
|
|
|
2010-08-05 21:22:23 +07:00
|
|
|
if (KDB_FLAG(CMD_INTERRUPT))
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!cnt)
|
|
|
|
kdb_printf(" (ftrace buffer empty)\n");
|
|
|
|
else
|
|
|
|
kdb_printf("---------------------------------\n");
|
|
|
|
|
|
|
|
out:
|
2015-09-30 20:42:05 +07:00
|
|
|
tr->trace_flags = old_userobj;
|
2010-08-05 21:22:23 +07:00
|
|
|
|
|
|
|
for_each_tracing_cpu(cpu) {
|
tracing: Consolidate max_tr into main trace_array structure
Currently, the way the latency tracers and snapshot feature works
is to have a separate trace_array called "max_tr" that holds the
snapshot buffer. For latency tracers, this snapshot buffer is used
to swap the running buffer with this buffer to save the current max
latency.
The only items needed for the max_tr is really just a copy of the buffer
itself, the per_cpu data pointers, the time_start timestamp that states
when the max latency was triggered, and the cpu that the max latency
was triggered on. All other fields in trace_array are unused by the
max_tr, making the max_tr mostly bloat.
This change removes the max_tr completely, and adds a new structure
called trace_buffer, that holds the buffer pointer, the per_cpu data
pointers, the time_start timestamp, and the cpu where the latency occurred.
The trace_array, now has two trace_buffers, one for the normal trace and
one for the max trace or snapshot. By doing this, not only do we remove
the bloat from the max_trace but the instances of traces can now use
their own snapshot feature and not have just the top level global_trace have
the snapshot feature and latency tracers for itself.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2013-03-05 21:24:35 +07:00
|
|
|
atomic_dec(&per_cpu_ptr(iter.trace_buffer->data, cpu)->disabled);
|
2010-08-05 21:22:23 +07:00
|
|
|
}
|
|
|
|
|
2014-11-06 19:41:55 +07:00
|
|
|
for_each_tracing_cpu(cpu) {
|
|
|
|
if (iter.buffer_iter[cpu]) {
|
2010-08-05 21:22:23 +07:00
|
|
|
ring_buffer_read_finish(iter.buffer_iter[cpu]);
|
2014-11-06 19:41:55 +07:00
|
|
|
iter.buffer_iter[cpu] = NULL;
|
|
|
|
}
|
|
|
|
}
|
2010-08-05 21:22:23 +07:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* kdb_ftdump - Dump the ftrace log buffer
|
|
|
|
*/
|
|
|
|
static int kdb_ftdump(int argc, const char **argv)
|
|
|
|
{
|
|
|
|
int skip_lines = 0;
|
2010-08-05 21:22:23 +07:00
|
|
|
long cpu_file;
|
2010-08-05 21:22:23 +07:00
|
|
|
char *cp;
|
|
|
|
|
2010-08-05 21:22:23 +07:00
|
|
|
if (argc > 2)
|
2010-08-05 21:22:23 +07:00
|
|
|
return KDB_ARGCOUNT;
|
|
|
|
|
|
|
|
if (argc) {
|
|
|
|
skip_lines = simple_strtol(argv[1], &cp, 0);
|
|
|
|
if (*cp)
|
|
|
|
skip_lines = 0;
|
|
|
|
}
|
|
|
|
|
2010-08-05 21:22:23 +07:00
|
|
|
if (argc == 2) {
|
|
|
|
cpu_file = simple_strtol(argv[2], &cp, 0);
|
|
|
|
if (*cp || cpu_file >= NR_CPUS || cpu_file < 0 ||
|
|
|
|
!cpu_online(cpu_file))
|
|
|
|
return KDB_BADINT;
|
|
|
|
} else {
|
2013-01-24 03:22:59 +07:00
|
|
|
cpu_file = RING_BUFFER_ALL_CPUS;
|
2010-08-05 21:22:23 +07:00
|
|
|
}
|
|
|
|
|
2010-08-05 21:22:23 +07:00
|
|
|
kdb_trap_printk++;
|
2010-08-05 21:22:23 +07:00
|
|
|
ftrace_dump_buf(skip_lines, cpu_file);
|
2010-08-05 21:22:23 +07:00
|
|
|
kdb_trap_printk--;
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static __init int kdb_ftrace_register(void)
|
|
|
|
{
|
2014-11-06 21:36:42 +07:00
|
|
|
kdb_register_flags("ftdump", kdb_ftdump, "[skip_#lines] [cpu]",
|
kdb: Categorize kdb commands (similar to SysRq categorization)
This patch introduces several new flags to collect kdb commands into
groups (later allowing them to be optionally disabled).
This follows similar prior art to enable/disable magic sysrq
commands.
The commands have been categorized as follows:
Always on: go (w/o args), env, set, help, ?, cpu (w/o args), sr,
dmesg, disable_nmi, defcmd, summary, grephelp
Mem read: md, mdr, mdp, mds, ef, bt (with args), per_cpu
Mem write: mm
Reg read: rd
Reg write: go (with args), rm
Inspect: bt (w/o args), btp, bta, btc, btt, ps, pid, lsmod
Flow ctrl: bp, bl, bph, bc, be, bd, ss
Signal: kill
Reboot: reboot
All: cpu, kgdb, (and all of the above), nmi_console
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
2014-11-06 21:36:45 +07:00
|
|
|
"Dump ftrace log", 0, KDB_ENABLE_ALWAYS_SAFE);
|
2010-08-05 21:22:23 +07:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
late_initcall(kdb_ftrace_register);
|