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 _LINUX_MMAN_H
|
|
|
|
|
#define _LINUX_MMAN_H
|
|
|
|
|
|
2006-04-25 21:18:07 +08:00
|
|
|
#include <linux/mm.h>
|
2009-05-01 06:08:51 +08:00
|
|
|
#include <linux/percpu_counter.h>
|
2006-04-25 21:18:07 +08:00
|
|
|
|
2011-07-27 07:09:06 +08:00
|
|
|
#include <linux/atomic.h>
|
2012-10-13 17:46:48 +08:00
|
|
|
#include <uapi/linux/mman.h>
|
2006-04-25 21:18:07 +08:00
|
|
|
|
mm: introduce MAP_SHARED_VALIDATE, a mechanism to safely define new mmap flags
The mmap(2) syscall suffers from the ABI anti-pattern of not validating
unknown flags. However, proposals like MAP_SYNC need a mechanism to
define new behavior that is known to fail on older kernels without the
support. Define a new MAP_SHARED_VALIDATE flag pattern that is
guaranteed to fail on all legacy mmap implementations.
It is worth noting that the original proposal was for a standalone
MAP_VALIDATE flag. However, when that could not be supported by all
archs Linus observed:
I see why you *think* you want a bitmap. You think you want
a bitmap because you want to make MAP_VALIDATE be part of MAP_SYNC
etc, so that people can do
ret = mmap(NULL, size, PROT_READ | PROT_WRITE, MAP_SHARED
| MAP_SYNC, fd, 0);
and "know" that MAP_SYNC actually takes.
And I'm saying that whole wish is bogus. You're fundamentally
depending on special semantics, just make it explicit. It's already
not portable, so don't try to make it so.
Rename that MAP_VALIDATE as MAP_SHARED_VALIDATE, make it have a value
of 0x3, and make people do
ret = mmap(NULL, size, PROT_READ | PROT_WRITE, MAP_SHARED_VALIDATE
| MAP_SYNC, fd, 0);
and then the kernel side is easier too (none of that random garbage
playing games with looking at the "MAP_VALIDATE bit", but just another
case statement in that map type thing.
Boom. Done.
Similar to ->fallocate() we also want the ability to validate the
support for new flags on a per ->mmap() 'struct file_operations'
instance basis. Towards that end arrange for flags to be generically
validated against a mmap_supported_flags exported by 'struct
file_operations'. By default all existing flags are implicitly
supported, but new flags require MAP_SHARED_VALIDATE and
per-instance-opt-in.
Cc: Jan Kara <jack@suse.cz>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Suggested-by: Christoph Hellwig <hch@lst.de>
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
2017-11-01 23:36:30 +08:00
|
|
|
/*
|
|
|
|
|
* Arrange for legacy / undefined architecture specific flags to be
|
2017-11-01 23:36:41 +08:00
|
|
|
* ignored by mmap handling code.
|
mm: introduce MAP_SHARED_VALIDATE, a mechanism to safely define new mmap flags
The mmap(2) syscall suffers from the ABI anti-pattern of not validating
unknown flags. However, proposals like MAP_SYNC need a mechanism to
define new behavior that is known to fail on older kernels without the
support. Define a new MAP_SHARED_VALIDATE flag pattern that is
guaranteed to fail on all legacy mmap implementations.
It is worth noting that the original proposal was for a standalone
MAP_VALIDATE flag. However, when that could not be supported by all
archs Linus observed:
I see why you *think* you want a bitmap. You think you want
a bitmap because you want to make MAP_VALIDATE be part of MAP_SYNC
etc, so that people can do
ret = mmap(NULL, size, PROT_READ | PROT_WRITE, MAP_SHARED
| MAP_SYNC, fd, 0);
and "know" that MAP_SYNC actually takes.
And I'm saying that whole wish is bogus. You're fundamentally
depending on special semantics, just make it explicit. It's already
not portable, so don't try to make it so.
Rename that MAP_VALIDATE as MAP_SHARED_VALIDATE, make it have a value
of 0x3, and make people do
ret = mmap(NULL, size, PROT_READ | PROT_WRITE, MAP_SHARED_VALIDATE
| MAP_SYNC, fd, 0);
and then the kernel side is easier too (none of that random garbage
playing games with looking at the "MAP_VALIDATE bit", but just another
case statement in that map type thing.
Boom. Done.
Similar to ->fallocate() we also want the ability to validate the
support for new flags on a per ->mmap() 'struct file_operations'
instance basis. Towards that end arrange for flags to be generically
validated against a mmap_supported_flags exported by 'struct
file_operations'. By default all existing flags are implicitly
supported, but new flags require MAP_SHARED_VALIDATE and
per-instance-opt-in.
Cc: Jan Kara <jack@suse.cz>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Suggested-by: Christoph Hellwig <hch@lst.de>
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
2017-11-01 23:36:30 +08:00
|
|
|
*/
|
|
|
|
|
#ifndef MAP_32BIT
|
|
|
|
|
#define MAP_32BIT 0
|
|
|
|
|
#endif
|
|
|
|
|
#ifndef MAP_HUGE_2MB
|
|
|
|
|
#define MAP_HUGE_2MB 0
|
|
|
|
|
#endif
|
|
|
|
|
#ifndef MAP_HUGE_1GB
|
|
|
|
|
#define MAP_HUGE_1GB 0
|
|
|
|
|
#endif
|
|
|
|
|
#ifndef MAP_UNINITIALIZED
|
|
|
|
|
#define MAP_UNINITIALIZED 0
|
|
|
|
|
#endif
|
2017-11-01 23:36:41 +08:00
|
|
|
#ifndef MAP_SYNC
|
|
|
|
|
#define MAP_SYNC 0
|
|
|
|
|
#endif
|
mm: introduce MAP_SHARED_VALIDATE, a mechanism to safely define new mmap flags
The mmap(2) syscall suffers from the ABI anti-pattern of not validating
unknown flags. However, proposals like MAP_SYNC need a mechanism to
define new behavior that is known to fail on older kernels without the
support. Define a new MAP_SHARED_VALIDATE flag pattern that is
guaranteed to fail on all legacy mmap implementations.
It is worth noting that the original proposal was for a standalone
MAP_VALIDATE flag. However, when that could not be supported by all
archs Linus observed:
I see why you *think* you want a bitmap. You think you want
a bitmap because you want to make MAP_VALIDATE be part of MAP_SYNC
etc, so that people can do
ret = mmap(NULL, size, PROT_READ | PROT_WRITE, MAP_SHARED
| MAP_SYNC, fd, 0);
and "know" that MAP_SYNC actually takes.
And I'm saying that whole wish is bogus. You're fundamentally
depending on special semantics, just make it explicit. It's already
not portable, so don't try to make it so.
Rename that MAP_VALIDATE as MAP_SHARED_VALIDATE, make it have a value
of 0x3, and make people do
ret = mmap(NULL, size, PROT_READ | PROT_WRITE, MAP_SHARED_VALIDATE
| MAP_SYNC, fd, 0);
and then the kernel side is easier too (none of that random garbage
playing games with looking at the "MAP_VALIDATE bit", but just another
case statement in that map type thing.
Boom. Done.
Similar to ->fallocate() we also want the ability to validate the
support for new flags on a per ->mmap() 'struct file_operations'
instance basis. Towards that end arrange for flags to be generically
validated against a mmap_supported_flags exported by 'struct
file_operations'. By default all existing flags are implicitly
supported, but new flags require MAP_SHARED_VALIDATE and
per-instance-opt-in.
Cc: Jan Kara <jack@suse.cz>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>
Suggested-by: Christoph Hellwig <hch@lst.de>
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
2017-11-01 23:36:30 +08:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* The historical set of flags that all mmap implementations implicitly
|
|
|
|
|
* support when a ->mmap_validate() op is not provided in file_operations.
|
|
|
|
|
*/
|
|
|
|
|
#define LEGACY_MAP_MASK (MAP_SHARED \
|
|
|
|
|
| MAP_PRIVATE \
|
|
|
|
|
| MAP_FIXED \
|
|
|
|
|
| MAP_ANONYMOUS \
|
|
|
|
|
| MAP_DENYWRITE \
|
|
|
|
|
| MAP_EXECUTABLE \
|
|
|
|
|
| MAP_UNINITIALIZED \
|
|
|
|
|
| MAP_GROWSDOWN \
|
|
|
|
|
| MAP_LOCKED \
|
|
|
|
|
| MAP_NORESERVE \
|
|
|
|
|
| MAP_POPULATE \
|
|
|
|
|
| MAP_NONBLOCK \
|
|
|
|
|
| MAP_STACK \
|
|
|
|
|
| MAP_HUGETLB \
|
|
|
|
|
| MAP_32BIT \
|
|
|
|
|
| MAP_HUGE_2MB \
|
|
|
|
|
| MAP_HUGE_1GB)
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
extern int sysctl_overcommit_memory;
|
|
|
|
|
extern int sysctl_overcommit_ratio;
|
2014-01-22 07:49:14 +08:00
|
|
|
extern unsigned long sysctl_overcommit_kbytes;
|
2009-05-01 06:08:51 +08:00
|
|
|
extern struct percpu_counter vm_committed_as;
|
2005-04-17 06:20:36 +08:00
|
|
|
|
2013-07-04 06:02:44 +08:00
|
|
|
#ifdef CONFIG_SMP
|
|
|
|
|
extern s32 vm_committed_as_batch;
|
|
|
|
|
#else
|
|
|
|
|
#define vm_committed_as_batch 0
|
|
|
|
|
#endif
|
|
|
|
|
|
2012-11-16 06:34:42 +08:00
|
|
|
unsigned long vm_memory_committed(void);
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
static inline void vm_acct_memory(long pages)
|
|
|
|
|
{
|
2017-06-21 02:01:20 +08:00
|
|
|
percpu_counter_add_batch(&vm_committed_as, pages, vm_committed_as_batch);
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static inline void vm_unacct_memory(long pages)
|
|
|
|
|
{
|
|
|
|
|
vm_acct_memory(-pages);
|
|
|
|
|
}
|
|
|
|
|
|
2008-07-07 22:28:51 +08:00
|
|
|
/*
|
|
|
|
|
* Allow architectures to handle additional protection bits
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef arch_calc_vm_prot_bits
|
2016-02-13 05:02:31 +08:00
|
|
|
#define arch_calc_vm_prot_bits(prot, pkey) 0
|
2008-07-07 22:28:51 +08:00
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifndef arch_vm_get_page_prot
|
|
|
|
|
#define arch_vm_get_page_prot(vm_flags) __pgprot(0)
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifndef arch_validate_prot
|
|
|
|
|
/*
|
|
|
|
|
* This is called from mprotect(). PROT_GROWSDOWN and PROT_GROWSUP have
|
|
|
|
|
* already been masked out.
|
|
|
|
|
*
|
|
|
|
|
* Returns true if the prot flags are valid
|
|
|
|
|
*/
|
2016-08-03 05:03:42 +08:00
|
|
|
static inline bool arch_validate_prot(unsigned long prot)
|
2008-07-07 22:28:51 +08:00
|
|
|
{
|
|
|
|
|
return (prot & ~(PROT_READ | PROT_WRITE | PROT_EXEC | PROT_SEM)) == 0;
|
|
|
|
|
}
|
|
|
|
|
#define arch_validate_prot arch_validate_prot
|
|
|
|
|
#endif
|
|
|
|
|
|
2005-04-17 06:20:36 +08:00
|
|
|
/*
|
|
|
|
|
* Optimisation macro. It is equivalent to:
|
|
|
|
|
* (x & bit1) ? bit2 : 0
|
|
|
|
|
* but this version is faster.
|
|
|
|
|
* ("bit1" and "bit2" must be single bits)
|
|
|
|
|
*/
|
|
|
|
|
#define _calc_vm_trans(x, bit1, bit2) \
|
2017-11-03 19:21:21 +08:00
|
|
|
((!(bit1) || !(bit2)) ? 0 : \
|
2005-04-17 06:20:36 +08:00
|
|
|
((bit1) <= (bit2) ? ((x) & (bit1)) * ((bit2) / (bit1)) \
|
2017-11-03 19:21:21 +08:00
|
|
|
: ((x) & (bit1)) / ((bit1) / (bit2))))
|
2005-04-17 06:20:36 +08:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Combine the mmap "prot" argument into "vm_flags" used internally.
|
|
|
|
|
*/
|
|
|
|
|
static inline unsigned long
|
2016-02-13 05:02:31 +08:00
|
|
|
calc_vm_prot_bits(unsigned long prot, unsigned long pkey)
|
2005-04-17 06:20:36 +08:00
|
|
|
{
|
|
|
|
|
return _calc_vm_trans(prot, PROT_READ, VM_READ ) |
|
|
|
|
|
_calc_vm_trans(prot, PROT_WRITE, VM_WRITE) |
|
2008-07-07 22:28:51 +08:00
|
|
|
_calc_vm_trans(prot, PROT_EXEC, VM_EXEC) |
|
2016-02-13 05:02:31 +08:00
|
|
|
arch_calc_vm_prot_bits(prot, pkey);
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Combine the mmap "flags" argument into "vm_flags" used internally.
|
|
|
|
|
*/
|
|
|
|
|
static inline unsigned long
|
|
|
|
|
calc_vm_flag_bits(unsigned long flags)
|
|
|
|
|
{
|
|
|
|
|
return _calc_vm_trans(flags, MAP_GROWSDOWN, VM_GROWSDOWN ) |
|
|
|
|
|
_calc_vm_trans(flags, MAP_DENYWRITE, VM_DENYWRITE ) |
|
2017-11-01 23:36:41 +08:00
|
|
|
_calc_vm_trans(flags, MAP_LOCKED, VM_LOCKED ) |
|
|
|
|
|
_calc_vm_trans(flags, MAP_SYNC, VM_SYNC );
|
2005-04-17 06:20:36 +08:00
|
|
|
}
|
2013-11-13 07:08:31 +08:00
|
|
|
|
|
|
|
|
unsigned long vm_commit_limit(void);
|
2005-04-17 06:20:36 +08:00
|
|
|
#endif /* _LINUX_MMAN_H */
|