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 08:07:57 -06:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2005-04-16 16:20:36 -06:00
|
|
|
#
|
|
|
|
|
# Makefile for the kernel software RAID and LVM drivers.
|
|
|
|
|
#
|
|
|
|
|
|
2009-03-30 21:27:02 -06:00
|
|
|
dm-mod-y += dm.o dm-table.o dm-target.o dm-linear.o dm-stripe.o \
|
2016-05-12 14:28:10 -06:00
|
|
|
dm-ioctl.o dm-io.o dm-kcopyd.o dm-sysfs.o dm-stats.o \
|
|
|
|
|
dm-rq.o
|
2009-03-30 21:27:02 -06:00
|
|
|
dm-multipath-y += dm-path-selector.o dm-mpath.o
|
|
|
|
|
dm-snapshot-y += dm-snap.o dm-exception-store.o dm-snap-transient.o \
|
2009-01-05 20:05:17 -07:00
|
|
|
dm-snap-persistent.o
|
2009-03-30 21:27:02 -06:00
|
|
|
dm-mirror-y += dm-raid1.o
|
2009-06-22 03:12:35 -06:00
|
|
|
dm-log-userspace-y \
|
|
|
|
|
+= dm-log-userspace-base.o dm-log-userspace-transfer.o
|
2016-10-21 08:06:40 -06:00
|
|
|
dm-bio-prison-y += dm-bio-prison-v1.o dm-bio-prison-v2.o
|
2011-10-31 14:21:18 -06:00
|
|
|
dm-thin-pool-y += dm-thin.o dm-thin-metadata.o
|
2016-12-15 02:57:31 -07:00
|
|
|
dm-cache-y += dm-cache-target.o dm-cache-metadata.o dm-cache-policy.o \
|
|
|
|
|
dm-cache-background-tracker.o
|
2015-05-15 08:33:34 -06:00
|
|
|
dm-cache-smq-y += dm-cache-policy-smq.o
|
2014-03-03 08:23:15 -07:00
|
|
|
dm-era-y += dm-era-target.o
|
dm: add clone target
Add the dm-clone target, which allows cloning of arbitrary block
devices.
dm-clone produces a one-to-one copy of an existing, read-only source
device into a writable destination device: It presents a virtual block
device which makes all data appear immediately, and redirects reads and
writes accordingly.
The main use case of dm-clone is to clone a potentially remote,
high-latency, read-only, archival-type block device into a writable,
fast, primary-type device for fast, low-latency I/O. The cloned device
is visible/mountable immediately and the copy of the source device to
the destination device happens in the background, in parallel with user
I/O.
When the cloning completes, the dm-clone table can be removed altogether
and be replaced, e.g., by a linear table, mapping directly to the
destination device.
For further information and examples of how to use dm-clone, please read
Documentation/admin-guide/device-mapper/dm-clone.rst
Suggested-by: Vangelis Koukis <vkoukis@arrikto.com>
Co-developed-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Signed-off-by: Nikos Tsironis <ntsironis@arrikto.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-09-11 08:36:40 -06:00
|
|
|
dm-clone-y += dm-clone-target.o dm-clone-metadata.o
|
2015-12-03 13:36:00 -07:00
|
|
|
dm-verity-y += dm-verity-target.o
|
2017-10-10 15:02:41 -06:00
|
|
|
md-mod-y += md.o md-bitmap.o
|
2017-03-09 01:59:59 -07:00
|
|
|
raid456-y += raid5.o raid5-cache.o raid5-ppl.o
|
2017-06-07 00:55:39 -06:00
|
|
|
dm-zoned-y += dm-zoned-target.o dm-zoned-metadata.o dm-zoned-reclaim.o
|
2017-10-10 15:02:41 -06:00
|
|
|
linear-y += md-linear.o
|
|
|
|
|
multipath-y += md-multipath.o
|
|
|
|
|
faulty-y += md-faulty.o
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
|
# Note: link order is important. All raid personalities
|
2007-07-09 12:56:42 -06:00
|
|
|
# and must come before md.o, as they each initialise
|
2005-04-16 16:20:36 -06:00
|
|
|
# themselves, and md.o may use the personalities when it
|
|
|
|
|
# auto-initialised.
|
|
|
|
|
|
|
|
|
|
obj-$(CONFIG_MD_LINEAR) += linear.o
|
|
|
|
|
obj-$(CONFIG_MD_RAID0) += raid0.o
|
|
|
|
|
obj-$(CONFIG_MD_RAID1) += raid1.o
|
|
|
|
|
obj-$(CONFIG_MD_RAID10) += raid10.o
|
2007-07-09 12:56:42 -06:00
|
|
|
obj-$(CONFIG_MD_RAID456) += raid456.o
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_MD_MULTIPATH) += multipath.o
|
|
|
|
|
obj-$(CONFIG_MD_FAULTY) += faulty.o
|
2014-03-07 10:21:15 -07:00
|
|
|
obj-$(CONFIG_MD_CLUSTER) += md-cluster.o
|
2013-03-23 17:11:31 -06:00
|
|
|
obj-$(CONFIG_BCACHE) += bcache/
|
2005-06-21 18:17:14 -06:00
|
|
|
obj-$(CONFIG_BLK_DEV_MD) += md-mod.o
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_BLK_DEV_DM) += dm-mod.o
|
2014-01-13 17:37:54 -07:00
|
|
|
obj-$(CONFIG_BLK_DEV_DM_BUILTIN) += dm-builtin.o
|
2017-12-18 10:28:08 -07:00
|
|
|
obj-$(CONFIG_DM_UNSTRIPED) += dm-unstripe.o
|
2011-10-31 14:19:09 -06:00
|
|
|
obj-$(CONFIG_DM_BUFIO) += dm-bufio.o
|
2012-10-12 14:02:13 -06:00
|
|
|
obj-$(CONFIG_DM_BIO_PRISON) += dm-bio-prison.o
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_DM_CRYPT) += dm-crypt.o
|
2007-05-09 03:33:06 -06:00
|
|
|
obj-$(CONFIG_DM_DELAY) += dm-delay.o
|
dm: add dust target
Add the dm-dust target, which simulates the behavior of bad sectors
at arbitrary locations, and the ability to enable the emulation of
the read failures at an arbitrary time.
This target behaves similarly to a linear target. At a given time,
the user can send a message to the target to start failing read
requests on specific blocks. When the failure behavior is enabled,
reads of blocks configured "bad" will fail with EIO.
Writes of blocks configured "bad" will result in the following:
1. Remove the block from the "bad block list".
2. Successfully complete the write.
After this point, the block will successfully contain the written
data, and will service reads and writes normally. This emulates the
behavior of a "remapped sector" on a hard disk drive.
dm-dust provides logging of which blocks have been added or removed
to the "bad block list", as well as logging when a block has been
removed from the bad block list. These messages can be used
alongside the messages from the driver using a dm-dust device to
analyze the driver's behavior when a read fails at a given time.
(This logging can be reduced via a "quiet" mode, if desired.)
NOTE: If the block size is larger than 512 bytes, only the first sector
of each "dust block" is detected. Placing a limiting layer above a dust
target, to limit the minimum I/O size to the dust block size, will
ensure proper emulation of the given large block size.
Signed-off-by: Bryan Gurney <bgurney@redhat.com>
Co-developed-by: Joe Shimkus <jshimkus@redhat.com>
Co-developed-by: John Dorminy <jdorminy@redhat.com>
Co-developed-by: John Pittman <jpittman@redhat.com>
Co-developed-by: Thomas Jaskiewicz <tjaskiew@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-03-07 13:42:39 -07:00
|
|
|
obj-$(CONFIG_DM_DUST) += dm-dust.o
|
2011-03-24 07:54:24 -06:00
|
|
|
obj-$(CONFIG_DM_FLAKEY) += dm-flakey.o
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_DM_MULTIPATH) += dm-multipath.o dm-round-robin.o
|
2009-06-22 03:12:27 -06:00
|
|
|
obj-$(CONFIG_DM_MULTIPATH_QL) += dm-queue-length.o
|
2009-06-22 03:12:28 -06:00
|
|
|
obj-$(CONFIG_DM_MULTIPATH_ST) += dm-service-time.o
|
2013-07-10 16:41:19 -06:00
|
|
|
obj-$(CONFIG_DM_SWITCH) += dm-switch.o
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_DM_SNAPSHOT) += dm-snapshot.o
|
2011-10-31 14:21:18 -06:00
|
|
|
obj-$(CONFIG_DM_PERSISTENT_DATA) += persistent-data/
|
2008-10-21 10:45:06 -06:00
|
|
|
obj-$(CONFIG_DM_MIRROR) += dm-mirror.o dm-log.o dm-region-hash.o
|
2009-06-22 03:12:35 -06:00
|
|
|
obj-$(CONFIG_DM_LOG_USERSPACE) += dm-log-userspace.o
|
2005-04-16 16:20:36 -06:00
|
|
|
obj-$(CONFIG_DM_ZERO) += dm-zero.o
|
dm: raid456 basic support
This patch is the skeleton for the DM target that will be
the bridge from DM to MD (initially RAID456 and later RAID1). It
provides a way to use device-mapper interfaces to the MD RAID456
drivers.
As with all device-mapper targets, the nominal public interfaces are the
constructor (CTR) tables and the status outputs (both STATUSTYPE_INFO
and STATUSTYPE_TABLE). The CTR table looks like the following:
1: <s> <l> raid \
2: <raid_type> <#raid_params> <raid_params> \
3: <#raid_devs> <meta_dev1> <dev1> .. <meta_devN> <devN>
Line 1 contains the standard first three arguments to any device-mapper
target - the start, length, and target type fields. The target type in
this case is "raid".
Line 2 contains the arguments that define the particular raid
type/personality/level, the required arguments for that raid type, and
any optional arguments. Possible raid types include: raid4, raid5_la,
raid5_ls, raid5_rs, raid6_zr, raid6_nr, and raid6_nc. (again, raid1 is
planned for the future.) The list of required and optional parameters
is the same for all the current raid types. The required parameters are
positional, while the optional parameters are given as key/value pairs.
The possible parameters are as follows:
<chunk_size> Chunk size in sectors.
[[no]sync] Force/Prevent RAID initialization
[rebuild <idx>] Rebuild the drive indicated by the index
[daemon_sleep <ms>] Time between bitmap daemon work to clear bits
[min_recovery_rate <kB/sec/disk>] Throttle RAID initialization
[max_recovery_rate <kB/sec/disk>] Throttle RAID initialization
[max_write_behind <value>] See '-write-behind=' (man mdadm)
[stripe_cache <sectors>] Stripe cache size for higher RAIDs
Line 3 contains the list of devices that compose the array in
metadata/data device pairs. If the metadata is stored separately, a '-'
is given for the metadata device position. If a drive has failed or is
missing at creation time, a '-' can be given for both the metadata and
data drives for a given position.
Examples:
# RAID4 - 4 data drives, 1 parity
# No metadata devices specified to hold superblock/bitmap info
# Chunk size of 1MiB
# (Lines separated for easy reading)
0 1960893648 raid \
raid4 1 2048 \
5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81
# RAID4 - 4 data drives, 1 parity (no metadata devices)
# Chunk size of 1MiB, force RAID initialization,
# min recovery rate at 20 kiB/sec/disk
0 1960893648 raid \
raid4 4 2048 min_recovery_rate 20 sync\
5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81
Performing a 'dmsetup table' should display the CTR table used to
construct the mapping (with possible reordering of optional
parameters).
Performing a 'dmsetup status' will yield information on the state and
health of the array. The output is as follows:
1: <s> <l> raid \
2: <raid_type> <#devices> <1 health char for each dev> <resync_ratio>
Line 1 is standard DM output. Line 2 is best shown by example:
0 1960893648 raid raid4 5 AAAAA 2/490221568
Here we can see the RAID type is raid4, there are 5 devices - all of
which are 'A'live, and the array is 2/490221568 complete with recovery.
Cc: linux-raid@vger.kernel.org
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
2011-01-13 13:00:02 -07:00
|
|
|
obj-$(CONFIG_DM_RAID) += dm-raid.o
|
2011-10-31 14:21:18 -06:00
|
|
|
obj-$(CONFIG_DM_THIN_PROVISIONING) += dm-thin-pool.o
|
2012-03-28 11:43:38 -06:00
|
|
|
obj-$(CONFIG_DM_VERITY) += dm-verity.o
|
2013-03-01 15:45:51 -07:00
|
|
|
obj-$(CONFIG_DM_CACHE) += dm-cache.o
|
2015-05-15 08:33:34 -06:00
|
|
|
obj-$(CONFIG_DM_CACHE_SMQ) += dm-cache-smq.o
|
2014-03-03 08:23:15 -07:00
|
|
|
obj-$(CONFIG_DM_ERA) += dm-era.o
|
dm: add clone target
Add the dm-clone target, which allows cloning of arbitrary block
devices.
dm-clone produces a one-to-one copy of an existing, read-only source
device into a writable destination device: It presents a virtual block
device which makes all data appear immediately, and redirects reads and
writes accordingly.
The main use case of dm-clone is to clone a potentially remote,
high-latency, read-only, archival-type block device into a writable,
fast, primary-type device for fast, low-latency I/O. The cloned device
is visible/mountable immediately and the copy of the source device to
the destination device happens in the background, in parallel with user
I/O.
When the cloning completes, the dm-clone table can be removed altogether
and be replaced, e.g., by a linear table, mapping directly to the
destination device.
For further information and examples of how to use dm-clone, please read
Documentation/admin-guide/device-mapper/dm-clone.rst
Suggested-by: Vangelis Koukis <vkoukis@arrikto.com>
Co-developed-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Signed-off-by: Nikos Tsironis <ntsironis@arrikto.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-09-11 08:36:40 -06:00
|
|
|
obj-$(CONFIG_DM_CLONE) += dm-clone.o
|
2015-03-20 08:50:37 -06:00
|
|
|
obj-$(CONFIG_DM_LOG_WRITES) += dm-log-writes.o
|
2017-01-04 12:23:53 -07:00
|
|
|
obj-$(CONFIG_DM_INTEGRITY) += dm-integrity.o
|
2017-06-07 00:55:39 -06:00
|
|
|
obj-$(CONFIG_DM_ZONED) += dm-zoned.o
|
2018-03-08 06:25:24 -07:00
|
|
|
obj-$(CONFIG_DM_WRITECACHE) += dm-writecache.o
|
2005-04-16 16:20:36 -06:00
|
|
|
|
dm: add support to directly boot to a mapped device
Add a "create" module parameter, which allows device-mapper targets to
be configured at boot time. This enables early use of DM targets in the
boot process (as the root device or otherwise) without the need of an
initramfs.
The syntax used in the boot param is based on the concise format from
the dmsetup tool to follow the rule of least surprise:
dmsetup table --concise /dev/mapper/lroot
Which is:
dm-mod.create=<name>,<uuid>,<minor>,<flags>,<table>[,<table>+][;<name>,<uuid>,<minor>,<flags>,<table>[,<table>+]+]
Where,
<name> ::= The device name.
<uuid> ::= xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx | ""
<minor> ::= The device minor number | ""
<flags> ::= "ro" | "rw"
<table> ::= <start_sector> <num_sectors> <target_type> <target_args>
<target_type> ::= "verity" | "linear" | ...
For example, the following could be added in the boot parameters:
dm-mod.create="lroot,,,rw, 0 4096 linear 98:16 0, 4096 4096 linear 98:32 0" root=/dev/dm-0
Only the targets that were tested are allowed and the ones that don't
change any block device when the device is create as read-only. For
example, mirror and cache targets are not allowed. The rationale behind
this is that if the user makes a mistake, choosing the wrong device to
be the mirror or the cache can corrupt data.
The only targets initially allowed are:
* crypt
* delay
* linear
* snapshot-origin
* striped
* verity
Co-developed-by: Will Drewry <wad@chromium.org>
Co-developed-by: Kees Cook <keescook@chromium.org>
Co-developed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Signed-off-by: Helen Koike <helen.koike@collabora.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-02-21 13:33:34 -07:00
|
|
|
ifeq ($(CONFIG_DM_INIT),y)
|
|
|
|
|
dm-mod-objs += dm-init.o
|
|
|
|
|
endif
|
|
|
|
|
|
2007-10-19 15:48:00 -06:00
|
|
|
ifeq ($(CONFIG_DM_UEVENT),y)
|
|
|
|
|
dm-mod-objs += dm-uevent.o
|
|
|
|
|
endif
|
2015-12-03 07:26:30 -07:00
|
|
|
|
|
|
|
|
ifeq ($(CONFIG_DM_VERITY_FEC),y)
|
|
|
|
|
dm-verity-objs += dm-verity-fec.o
|
|
|
|
|
endif
|
2019-07-17 18:46:15 -06:00
|
|
|
|
|
|
|
|
ifeq ($(CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG),y)
|
|
|
|
|
dm-verity-objs += dm-verity-verify-sig.o
|
|
|
|
|
endif
|