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
|
|
|
#ifndef _SCSI_SCSI_DEVINFO_H
|
|
|
|
|
#define _SCSI_SCSI_DEVINFO_H
|
|
|
|
|
/*
|
|
|
|
|
* Flags for SCSI devices that need special treatment
|
|
|
|
|
*/
|
2017-10-02 22:26:35 +08:00
|
|
|
|
|
|
|
|
/* Only scan LUN 0 */
|
|
|
|
|
#define BLIST_NOLUN ((__force __u32 __bitwise)(1 << 0))
|
|
|
|
|
/* Known to have LUNs, force scanning.
|
|
|
|
|
* DEPRECATED: Use max_luns=N */
|
|
|
|
|
#define BLIST_FORCELUN ((__force __u32 __bitwise)(1 << 1))
|
|
|
|
|
/* Flag for broken handshaking */
|
|
|
|
|
#define BLIST_BORKEN ((__force __u32 __bitwise)(1 << 2))
|
|
|
|
|
/* unlock by special command */
|
|
|
|
|
#define BLIST_KEY ((__force __u32 __bitwise)(1 << 3))
|
|
|
|
|
/* Do not use LUNs in parallel */
|
|
|
|
|
#define BLIST_SINGLELUN ((__force __u32 __bitwise)(1 << 4))
|
|
|
|
|
/* Buggy Tagged Command Queuing */
|
|
|
|
|
#define BLIST_NOTQ ((__force __u32 __bitwise)(1 << 5))
|
|
|
|
|
/* Non consecutive LUN numbering */
|
|
|
|
|
#define BLIST_SPARSELUN ((__force __u32 __bitwise)(1 << 6))
|
|
|
|
|
/* Avoid LUNS >= 5 */
|
|
|
|
|
#define BLIST_MAX5LUN ((__force __u32 __bitwise)(1 << 7))
|
|
|
|
|
/* Treat as (removable) CD-ROM */
|
|
|
|
|
#define BLIST_ISROM ((__force __u32 __bitwise)(1 << 8))
|
|
|
|
|
/* LUNs past 7 on a SCSI-2 device */
|
|
|
|
|
#define BLIST_LARGELUN ((__force __u32 __bitwise)(1 << 9))
|
|
|
|
|
/* override additional length field */
|
|
|
|
|
#define BLIST_INQUIRY_36 ((__force __u32 __bitwise)(1 << 10))
|
|
|
|
|
/* do not do automatic start on add */
|
|
|
|
|
#define BLIST_NOSTARTONADD ((__force __u32 __bitwise)(1 << 12))
|
|
|
|
|
/* try REPORT_LUNS even for SCSI-2 devs (if HBA supports more than 8 LUNs) */
|
|
|
|
|
#define BLIST_REPORTLUN2 ((__force __u32 __bitwise)(1 << 17))
|
|
|
|
|
/* don't try REPORT_LUNS scan (SCSI-3 devs) */
|
|
|
|
|
#define BLIST_NOREPORTLUN ((__force __u32 __bitwise)(1 << 18))
|
|
|
|
|
/* don't use PREVENT-ALLOW commands */
|
|
|
|
|
#define BLIST_NOT_LOCKABLE ((__force __u32 __bitwise)(1 << 19))
|
|
|
|
|
/* device is actually for RAID config */
|
|
|
|
|
#define BLIST_NO_ULD_ATTACH ((__force __u32 __bitwise)(1 << 20))
|
|
|
|
|
/* select without ATN */
|
|
|
|
|
#define BLIST_SELECT_NO_ATN ((__force __u32 __bitwise)(1 << 21))
|
|
|
|
|
/* retry HARDWARE_ERROR */
|
|
|
|
|
#define BLIST_RETRY_HWERROR ((__force __u32 __bitwise)(1 << 22))
|
|
|
|
|
/* maximum 512 sector cdb length */
|
|
|
|
|
#define BLIST_MAX_512 ((__force __u32 __bitwise)(1 << 23))
|
|
|
|
|
/* Disable T10 PI (DIF) */
|
|
|
|
|
#define BLIST_NO_DIF ((__force __u32 __bitwise)(1 << 25))
|
|
|
|
|
/* Ignore SBC-3 VPD pages */
|
|
|
|
|
#define BLIST_SKIP_VPD_PAGES ((__force __u32 __bitwise)(1 << 26))
|
|
|
|
|
/* Attempt to read VPD pages */
|
|
|
|
|
#define BLIST_TRY_VPD_PAGES ((__force __u32 __bitwise)(1 << 28))
|
|
|
|
|
/* don't try to issue RSOC */
|
|
|
|
|
#define BLIST_NO_RSOC ((__force __u32 __bitwise)(1 << 29))
|
|
|
|
|
/* maximum 1024 sector cdb length */
|
|
|
|
|
#define BLIST_MAX_1024 ((__force __u32 __bitwise)(1 << 30))
|
SCSI misc on 20171114
This is mostly updates of the usual suspects: lpfc, qla2xxx, hisi_sas,
megaraid_sas, pm80xx, mpt3sas, be2iscsi, hpsa. and a host of minor
updates.
There's no major behaviour change or additions to the core in all of
this, so the potential for regressions should be small (biggest
potential being in the scsi error handler changes).
Signed-off-by: James E.J. Bottomley <jejb@linux.vnet.ibm.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAABAgAGBQJaCxtCAAoJEAVr7HOZEZN4d9EQAI+OHP6ss6zjKKC21c9jNPcH
NhLrNv37gHg/LA2VXeUEL9RGUjCGLIUrI4HsrxzkFAMLKP4TkshMs8/2RvczY+Sa
VpayPqVybEKLIS6ipQyM1SLIQff2nvtDVcN/T+8z1lkk45TrbA6ZGuwUwd2aJyEA
2V2wtg51ObnL0Nr9QPPll0JrtL1AnCZyRlu9XrwTZuuSBZwk93opIuuvbZm/3dVg
Ir4GSS4Y+PuHIfu4cxqdsPMdzRdY9I2me1YiE4jeFSn1/VTAjL4HBz7fO9eITT42
VhXSpDz1XvFsa9dJ0ubkqoALpJzCfOcBw+EuGvSydLEvOBoEVwMccdfaD9lT1zc5
L9e1Z5qqJoq7hTA6xTXCYfWG73I9HYvljtmc8yudKHhADOdnSTUXhaO6uBF0RNqD
OxPSA1RZwRx3c6lDOcK6BTtvLAkTEuYKdrWSKJi0w+QXJAyQ6etqbmsKpmPdRim7
Z4ZSpJFro2gyo9gcdJO0ykTG+z3U7Z/ay1sNgnuprsv+eU/QjUdlAPl18o79EkRf
H54zZggZ4wC6q/cFVVt4Vx+V+oqIeu38s7NDXS9UltLoTZPm2EzDW6pXd/38Z4Tf
a1oBAUET8kYLC90P8sVZxUIHZjITlpgDbyE2Lq00PMYXhk8S4IxF0aMN5RvVqzUv
+7N2HrHkSSgG1nhw1t+E
=3O85
-----END PGP SIGNATURE-----
Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi
Pull SCSI updates from James Bottomley:
"This is mostly updates of the usual suspects: lpfc, qla2xxx, hisi_sas,
megaraid_sas, pm80xx, mpt3sas, be2iscsi, hpsa. and a host of minor
updates.
There's no major behaviour change or additions to the core in all of
this, so the potential for regressions should be small (biggest
potential being in the scsi error handler changes)"
* tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi: (203 commits)
scsi: lpfc: Fix hard lock up NMI in els timeout handling.
scsi: mpt3sas: remove a stray KERN_INFO
scsi: mpt3sas: cleanup _scsih_pcie_enumeration_event()
scsi: aacraid: use timespec64 instead of timeval
scsi: scsi_transport_fc: add 64GBIT and 128GBIT port speed definitions
scsi: qla2xxx: Suppress a kernel complaint in qla_init_base_qpair()
scsi: mpt3sas: fix dma_addr_t casts
scsi: be2iscsi: Use kasprintf
scsi: storvsc: Avoid excessive host scan on controller change
scsi: lpfc: fix kzalloc-simple.cocci warnings
scsi: mpt3sas: Update mpt3sas driver version.
scsi: mpt3sas: Fix sparse warnings
scsi: mpt3sas: Fix nvme drives checking for tlr.
scsi: mpt3sas: NVMe drive support for BTDHMAPPING ioctl command and log info
scsi: mpt3sas: Add-Task-management-debug-info-for-NVMe-drives.
scsi: mpt3sas: scan and add nvme device after controller reset
scsi: mpt3sas: Set NVMe device queue depth as 128
scsi: mpt3sas: Handle NVMe PCIe device related events generated from firmware.
scsi: mpt3sas: API's to remove nvme drive from sml
scsi: mpt3sas: API 's to support NVMe drive addition to SML
...
2017-11-15 08:23:44 +08:00
|
|
|
/* Use UNMAP limit for WRITE SAME */
|
|
|
|
|
#define BLIST_UNMAP_LIMIT_WS ((__force __u32 __bitwise)(1 << 31))
|
2014-07-24 21:48:46 +08:00
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
#endif
|