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
|
|
|
/*
|
|
|
|
|
The compile-time configurable defaults for the Linux SCSI tape driver.
|
|
|
|
|
|
|
|
|
|
Copyright 1995-2003 Kai Makisara.
|
|
|
|
|
|
2008-02-25 04:23:24 +08:00
|
|
|
Last modified: Thu Feb 21 21:47:07 2008 by kai.makisara
|
2005-04-17 06:20:36 +08:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef _ST_OPTIONS_H
|
|
|
|
|
#define _ST_OPTIONS_H
|
|
|
|
|
|
|
|
|
|
/* If TRY_DIRECT_IO is non-zero, the driver tries to transfer data directly
|
|
|
|
|
between the user buffer and tape drive. If this is not possible, driver
|
|
|
|
|
buffer is used. If TRY_DIRECT_IO is zero, driver buffer is always used. */
|
|
|
|
|
#define TRY_DIRECT_IO 1
|
|
|
|
|
|
|
|
|
|
/* The driver does not wait for some operations to finish before returning
|
|
|
|
|
to the user program if ST_NOWAIT is non-zero. This helps if the SCSI
|
|
|
|
|
adapter does not support multiple outstanding commands. However, the user
|
|
|
|
|
should not give a new tape command before the previous one has finished. */
|
|
|
|
|
#define ST_NOWAIT 0
|
|
|
|
|
|
|
|
|
|
/* If ST_IN_FILE_POS is nonzero, the driver positions the tape after the
|
|
|
|
|
record been read by the user program even if the tape has moved further
|
|
|
|
|
because of buffered reads. Should be set to zero to support also drives
|
|
|
|
|
that can't space backwards over records. NOTE: The tape will be
|
|
|
|
|
spaced backwards over an "accidentally" crossed filemark in any case. */
|
|
|
|
|
#define ST_IN_FILE_POS 0
|
|
|
|
|
|
|
|
|
|
/* If ST_RECOVERED_WRITE_FATAL is non-zero, recovered errors while writing
|
|
|
|
|
are considered "hard errors". */
|
|
|
|
|
#define ST_RECOVERED_WRITE_FATAL 0
|
|
|
|
|
|
|
|
|
|
/* The "guess" for the block size for devices that don't support MODE
|
|
|
|
|
SENSE. */
|
|
|
|
|
#define ST_DEFAULT_BLOCK 0
|
|
|
|
|
|
|
|
|
|
/* The minimum tape driver buffer size in kilobytes in fixed block mode.
|
|
|
|
|
Must be non-zero. */
|
|
|
|
|
#define ST_FIXED_BUFFER_BLOCKS 32
|
|
|
|
|
|
|
|
|
|
/* Maximum number of scatter/gather segments */
|
|
|
|
|
#define ST_MAX_SG 256
|
|
|
|
|
|
|
|
|
|
/* The number of scatter/gather segments to allocate at first try (must be
|
|
|
|
|
smaller or equal to the maximum). */
|
|
|
|
|
#define ST_FIRST_SG 8
|
|
|
|
|
|
|
|
|
|
/* The size of the first scatter/gather segments (determines the maximum block
|
|
|
|
|
size for SCSI adapters not supporting scatter/gather). The default is set
|
|
|
|
|
to try to allocate the buffer as one chunk. */
|
|
|
|
|
#define ST_FIRST_ORDER 5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/* The following lines define defaults for properties that can be set
|
|
|
|
|
separately for each drive using the MTSTOPTIONS ioctl. */
|
|
|
|
|
|
|
|
|
|
/* If ST_TWO_FM is non-zero, the driver writes two filemarks after a
|
|
|
|
|
file being written. Some drives can't handle two filemarks at the
|
|
|
|
|
end of data. */
|
|
|
|
|
#define ST_TWO_FM 0
|
|
|
|
|
|
|
|
|
|
/* If ST_BUFFER_WRITES is non-zero, writes in fixed block mode are
|
|
|
|
|
buffered until the driver buffer is full or asynchronous write is
|
|
|
|
|
triggered. May make detection of End-Of-Medium early enough fail. */
|
|
|
|
|
#define ST_BUFFER_WRITES 1
|
|
|
|
|
|
|
|
|
|
/* If ST_ASYNC_WRITES is non-zero, the SCSI write command may be started
|
|
|
|
|
without waiting for it to finish. May cause problems in multiple
|
|
|
|
|
tape backups. */
|
|
|
|
|
#define ST_ASYNC_WRITES 1
|
|
|
|
|
|
|
|
|
|
/* If ST_READ_AHEAD is non-zero, blocks are read ahead in fixed block
|
|
|
|
|
mode. */
|
|
|
|
|
#define ST_READ_AHEAD 1
|
|
|
|
|
|
|
|
|
|
/* If ST_AUTO_LOCK is non-zero, the drive door is locked at the first
|
|
|
|
|
read or write command after the device is opened. The door is opened
|
|
|
|
|
when the device is closed. */
|
|
|
|
|
#define ST_AUTO_LOCK 0
|
|
|
|
|
|
|
|
|
|
/* If ST_FAST_MTEOM is non-zero, the MTEOM ioctl is done using the
|
|
|
|
|
direct SCSI command. The file number status is lost but this method
|
|
|
|
|
is fast with some drives. Otherwise MTEOM is done by spacing over
|
|
|
|
|
files and the file number status is retained. */
|
|
|
|
|
#define ST_FAST_MTEOM 0
|
|
|
|
|
|
|
|
|
|
/* If ST_SCSI2LOGICAL is nonzero, the logical block addresses are used for
|
|
|
|
|
MTIOCPOS and MTSEEK by default. Vendor addresses are used if ST_SCSI2LOGICAL
|
|
|
|
|
is zero. */
|
|
|
|
|
#define ST_SCSI2LOGICAL 0
|
|
|
|
|
|
|
|
|
|
/* If ST_SYSV is non-zero, the tape behaves according to the SYS V semantics.
|
|
|
|
|
The default is BSD semantics. */
|
|
|
|
|
#define ST_SYSV 0
|
|
|
|
|
|
2008-02-25 04:23:24 +08:00
|
|
|
/* If ST_SILI is non-zero, the SILI bit is set when reading in variable block
|
|
|
|
|
mode and the block size is determined using the residual returned by the HBA. */
|
|
|
|
|
#define ST_SILI 0
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
/* Time to wait for the drive to become ready if blocking open */
|
|
|
|
|
#define ST_BLOCK_SECONDS 120
|
|
|
|
|
|
|
|
|
|
#endif
|