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 17:07:57 +03:00
/* SPDX-License-Identifier: GPL-2.0 */
2006-11-30 16:53:54 +03:00
# ifdef CONFIG_MMU
ARM: 7645/1: ioremap: introduce an infrastructure for static mapped area
In current implementation, we used ARM-specific flag, that is,
VM_ARM_STATIC_MAPPING, for distinguishing ARM specific static mapped area.
The purpose of static mapped area is to re-use static mapped area when
entire physical address range of the ioremap request can be covered
by this area.
This implementation causes needless overhead for some cases.
For example, assume that there is only one static mapped area and
vmlist has 300 areas. Every time we call ioremap, we check 300 areas for
deciding whether it is matched or not. Moreover, even if there is
no static mapped area and vmlist has 300 areas, every time we call
ioremap, we check 300 areas in now.
If we construct a extra list for static mapped area, we can eliminate
above mentioned overhead.
With a extra list, if there is one static mapped area,
we just check only one area and proceed next operation quickly.
In fact, it is not a critical problem, because ioremap is not frequently
used. But reducing overhead is better idea.
Another reason for doing this work is for removing architecture dependency
on vmalloc layer. I think that vmlist and vmlist_lock is internal data
structure for vmalloc layer. Some codes for debugging and stat inevitably
use vmlist and vmlist_lock. But it is preferable that they are used
as least as possible in outside of vmalloc.c
Now, I introduce an ARM-specific infrastructure for static mapped area. In
the following patch, we will use this and resolve above mentioned problem.
Reviewed-by: Nicolas Pitre <nico@linaro.org>
Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2013-02-09 09:28:05 +04:00
# include <linux/list.h>
# include <linux/vmalloc.h>
2006-11-30 16:53:54 +03:00
2014-04-13 21:57:29 +04:00
# include <asm/pgtable.h>
2008-09-16 21:05:53 +04:00
/* the upper-most page table pointer */
2006-08-21 20:06:38 +04:00
extern pmd_t * top_pmd ;
2011-07-02 17:46:27 +04:00
/*
* 0xffff8000 to 0xffffffff is reserved for any ARM architecture
* specific hacks for copying pages efficiently , while 0xffff4000
* is reserved for VIPT aliasing flushing by generic code .
*
* Note that we don ' t allow VIPT aliasing caches with SMP .
*/
# define COPYPAGE_MINICACHE 0xffff8000
# define COPYPAGE_V6_FROM 0xffff8000
# define COPYPAGE_V6_TO 0xffffc000
/* PFN alias flushing, for VIPT caches */
# define FLUSH_ALIAS_START 0xffff4000
2011-07-02 18:20:44 +04:00
static inline void set_top_pte ( unsigned long va , pte_t pte )
{
2011-07-04 14:25:53 +04:00
pte_t * ptep = pte_offset_kernel ( top_pmd , va ) ;
set_pte_ext ( ptep , pte , 0 ) ;
2011-07-02 18:20:44 +04:00
local_flush_tlb_kernel_page ( va ) ;
}
2011-07-04 14:22:27 +04:00
static inline pte_t get_top_pte ( unsigned long va )
{
2011-07-04 14:25:53 +04:00
pte_t * ptep = pte_offset_kernel ( top_pmd , va ) ;
return * ptep ;
2011-07-04 14:22:27 +04:00
}
2006-08-21 20:06:38 +04:00
static inline pmd_t * pmd_off_k ( unsigned long virt )
{
2011-05-26 22:50:30 +04:00
return pmd_offset ( pud_offset ( pgd_offset_k ( virt ) , virt ) , virt ) ;
2006-08-21 20:06:38 +04:00
}
2007-04-21 13:47:29 +04:00
struct mem_type {
2010-11-16 03:22:09 +03:00
pteval_t prot_pte ;
2014-02-03 01:21:31 +04:00
pteval_t prot_pte_s2 ;
2011-09-05 20:51:56 +04:00
pmdval_t prot_l1 ;
pmdval_t prot_sect ;
2007-04-21 13:47:29 +04:00
unsigned int domain ;
} ;
const struct mem_type * get_mem_type ( unsigned int type ) ;
2009-10-24 17:11:59 +04:00
extern void __flush_dcache_page ( struct address_space * mapping , struct page * page ) ;
2011-09-16 09:14:23 +04:00
/*
* ARM specific vm_struct - > flags bits .
*/
/* (super)section-mapped I/O regions used by ioremap()/iounmap() */
# define VM_ARM_SECTION_MAPPING 0x80000000
/* permanent static mappings from iotable_init() */
# define VM_ARM_STATIC_MAPPING 0x40000000
2012-08-25 12:03:15 +04:00
/* empty mapping */
# define VM_ARM_EMPTY_MAPPING 0x20000000
2011-09-16 09:14:23 +04:00
/* mapping type (attributes) for permanent static mappings */
# define VM_ARM_MTYPE(mt) ((mt) << 20)
# define VM_ARM_MTYPE_MASK (0x1f << 20)
2012-07-30 11:11:33 +04:00
/* consistent regions used by dma_alloc_attrs() */
# define VM_ARM_DMA_CONSISTENT 0x20000000
ARM: 7645/1: ioremap: introduce an infrastructure for static mapped area
In current implementation, we used ARM-specific flag, that is,
VM_ARM_STATIC_MAPPING, for distinguishing ARM specific static mapped area.
The purpose of static mapped area is to re-use static mapped area when
entire physical address range of the ioremap request can be covered
by this area.
This implementation causes needless overhead for some cases.
For example, assume that there is only one static mapped area and
vmlist has 300 areas. Every time we call ioremap, we check 300 areas for
deciding whether it is matched or not. Moreover, even if there is
no static mapped area and vmlist has 300 areas, every time we call
ioremap, we check 300 areas in now.
If we construct a extra list for static mapped area, we can eliminate
above mentioned overhead.
With a extra list, if there is one static mapped area,
we just check only one area and proceed next operation quickly.
In fact, it is not a critical problem, because ioremap is not frequently
used. But reducing overhead is better idea.
Another reason for doing this work is for removing architecture dependency
on vmalloc layer. I think that vmlist and vmlist_lock is internal data
structure for vmalloc layer. Some codes for debugging and stat inevitably
use vmlist and vmlist_lock. But it is preferable that they are used
as least as possible in outside of vmalloc.c
Now, I introduce an ARM-specific infrastructure for static mapped area. In
the following patch, we will use this and resolve above mentioned problem.
Reviewed-by: Nicolas Pitre <nico@linaro.org>
Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2013-02-09 09:28:05 +04:00
struct static_vm {
struct vm_struct vm ;
struct list_head list ;
} ;
extern struct list_head static_vmlist ;
extern struct static_vm * find_static_vm_vaddr ( void * vaddr ) ;
extern __init void add_static_vm_early ( struct static_vm * svm ) ;
2006-11-30 16:53:54 +03:00
# endif
2011-07-09 00:26:59 +04:00
# ifdef CONFIG_ZONE_DMA
2012-06-06 14:05:01 +04:00
extern phys_addr_t arm_dma_limit ;
2013-07-09 15:14:49 +04:00
extern unsigned long arm_dma_pfn_limit ;
2011-07-09 00:26:59 +04:00
# else
2012-07-05 16:11:31 +04:00
# define arm_dma_limit ((phys_addr_t)~0)
2013-07-09 15:14:49 +04:00
# define arm_dma_pfn_limit (~0ul >> PAGE_SHIFT)
2011-07-09 00:26:59 +04:00
# endif
2011-12-29 16:09:51 +04:00
extern phys_addr_t arm_lowmem_limit ;
2010-05-22 22:47:18 +04:00
void __init bootmem_init ( void ) ;
2010-07-09 19:27:52 +04:00
void arm_mm_memblock_reserve ( void ) ;
2011-12-29 16:09:51 +04:00
void dma_contiguous_remap ( void ) ;
2014-04-13 21:57:29 +04:00
unsigned long __clear_cr ( unsigned long mask ) ;
