mirror of
https://mirrors.bfsu.edu.cn/git/linux.git
synced 2024-11-13 23:34:05 +08:00
b24413180f
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>
108 lines
4.1 KiB
C
108 lines
4.1 KiB
C
/* SPDX-License-Identifier: GPL-2.0 */
|
|
/*
|
|
The compile-time configurable defaults for the Linux SCSI tape driver.
|
|
|
|
Copyright 1995 Kai Makisara.
|
|
|
|
Last modified: Wed Sep 2 21:24:07 1998 by root@home
|
|
|
|
Changed (and renamed) for OnStream SCSI drives garloff@suse.de
|
|
2000-06-21
|
|
|
|
$Header: /cvsroot/osst/Driver/osst_options.h,v 1.6 2003/12/23 14:22:12 wriede Exp $
|
|
*/
|
|
|
|
#ifndef _OSST_OPTIONS_H
|
|
#define _OSST_OPTIONS_H
|
|
|
|
/* The minimum limit for the number of SCSI tape devices is determined by
|
|
OSST_MAX_TAPES. If the number of tape devices and the "slack" defined by
|
|
OSST_EXTRA_DEVS exceeds OSST_MAX_TAPES, the large number is used. */
|
|
#define OSST_MAX_TAPES 4
|
|
|
|
/* If OSST_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 OSST_IN_FILE_POS 1
|
|
|
|
/* The tape driver buffer size in kilobytes. */
|
|
/* Don't change, as this is the HW blocksize */
|
|
#define OSST_BUFFER_BLOCKS 32
|
|
|
|
/* The number of kilobytes of data in the buffer that triggers an
|
|
asynchronous write in fixed block mode. See also OSST_ASYNC_WRITES
|
|
below. */
|
|
#define OSST_WRITE_THRESHOLD_BLOCKS 32
|
|
|
|
/* OSST_EOM_RESERVE defines the number of frames are kept in reserve for
|
|
* * write error recovery when writing near end of medium. ENOSPC is returned
|
|
* * when write() is called and the tape write position is within this number
|
|
* * of blocks from the tape capacity. */
|
|
#define OSST_EOM_RESERVE 300
|
|
|
|
/* The maximum number of tape buffers the driver allocates. The number
|
|
is also constrained by the number of drives detected. Determines the
|
|
maximum number of concurrently active tape drives. */
|
|
#define OSST_MAX_BUFFERS OSST_MAX_TAPES
|
|
|
|
/* Maximum number of scatter/gather segments */
|
|
/* Fit one buffer in pages and add one for the AUX header */
|
|
#define OSST_MAX_SG (((OSST_BUFFER_BLOCKS*1024) / PAGE_SIZE) + 1)
|
|
|
|
/* The number of scatter/gather segments to allocate at first try (must be
|
|
smaller or equal to the maximum). */
|
|
#define OSST_FIRST_SG ((OSST_BUFFER_BLOCKS*1024) / PAGE_SIZE)
|
|
|
|
/* 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 OSST_FIRST_ORDER (15-PAGE_SHIFT)
|
|
|
|
|
|
/* The following lines define defaults for properties that can be set
|
|
separately for each drive using the MTSTOPTIONS ioctl. */
|
|
|
|
/* If OSST_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 OSST_TWO_FM 0
|
|
|
|
/* If OSST_BUFFER_WRITES is non-zero, writes in fixed block mode are
|
|
buffered until the driver buffer is full or asynchronous write is
|
|
triggered. */
|
|
#define OSST_BUFFER_WRITES 1
|
|
|
|
/* If OSST_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 OSST_ASYNC_WRITES 1
|
|
|
|
/* If OSST_READ_AHEAD is non-zero, blocks are read ahead in fixed block
|
|
mode. */
|
|
#define OSST_READ_AHEAD 1
|
|
|
|
/* If OSST_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 OSST_AUTO_LOCK 0
|
|
|
|
/* If OSST_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 OSST_FAST_MTEOM 0
|
|
|
|
/* If OSST_SCSI2LOGICAL is nonzero, the logical block addresses are used for
|
|
MTIOCPOS and MTSEEK by default. Vendor addresses are used if OSST_SCSI2LOGICAL
|
|
is zero. */
|
|
#define OSST_SCSI2LOGICAL 0
|
|
|
|
/* If OSST_SYSV is non-zero, the tape behaves according to the SYS V semantics.
|
|
The default is BSD semantics. */
|
|
#define OSST_SYSV 0
|
|
|
|
|
|
#endif
|