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
2014-10-10 02:28:37 +04:00
/*
* mm / debug . c
*
* mm / specific debug routines .
*
*/
2014-10-10 02:28:34 +04:00
# include <linux/kernel.h>
# include <linux/mm.h>
2015-04-29 21:36:05 +03:00
# include <linux/trace_events.h>
2014-10-10 02:28:34 +04:00
# include <linux/memcontrol.h>
mm, tracing: unify mm flags handling in tracepoints and printk
In tracepoints, it's possible to print gfp flags in a human-friendly
format through a macro show_gfp_flags(), which defines a translation
array and passes is to __print_flags(). Since the following patch will
introduce support for gfp flags printing in printk(), it would be nice
to reuse the array. This is not straightforward, since __print_flags()
can't simply reference an array defined in a .c file such as mm/debug.c
- it has to be a macro to allow the macro magic to communicate the
format to userspace tools such as trace-cmd.
The solution is to create a macro __def_gfpflag_names which is used both
in show_gfp_flags(), and to define the gfpflag_names[] array in
mm/debug.c.
On the other hand, mm/debug.c also defines translation tables for page
flags and vma flags, and desire was expressed (but not implemented in
this series) to use these also from tracepoints. Thus, this patch also
renames the events/gfpflags.h file to events/mmflags.h and moves the
table definitions there, using the same macro approach as for gfpflags.
This allows translating all three kinds of mm-specific flags both in
tracepoints and printk.
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Reviewed-by: Michal Hocko <mhocko@suse.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Sasha Levin <sasha.levin@oracle.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Mel Gorman <mgorman@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-03-16 00:55:52 +03:00
# include <trace/events/mmflags.h>
2016-03-16 00:56:18 +03:00
# include <linux/migrate.h>
2016-03-16 00:56:21 +03:00
# include <linux/page_owner.h>
2014-10-10 02:28:34 +04:00
mm, printk: introduce new format string for flags
In mm we use several kinds of flags bitfields that are sometimes printed
for debugging purposes, or exported to userspace via sysfs. To make
them easier to interpret independently on kernel version and config, we
want to dump also the symbolic flag names. So far this has been done
with repeated calls to pr_cont(), which is unreliable on SMP, and not
usable for e.g. sysfs export.
To get a more reliable and universal solution, this patch extends
printk() format string for pointers to handle the page flags (%pGp),
gfp_flags (%pGg) and vma flags (%pGv). Existing users of
dump_flag_names() are converted and simplified.
It would be possible to pass flags by value instead of pointer, but the
%p format string for pointers already has extensions for various kernel
structures, so it's a good fit, and the extra indirection in a
non-critical path is negligible.
[linux@rasmusvillemoes.dk: lots of good implementation suggestions]
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Acked-by: Michal Hocko <mhocko@suse.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Sasha Levin <sasha.levin@oracle.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Mel Gorman <mgorman@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-03-16 00:55:56 +03:00
# include "internal.h"
2016-03-16 00:56:18 +03:00
char * migrate_reason_names [ MR_TYPES ] = {
" compaction " ,
" memory_failure " ,
" memory_hotplug " ,
" syscall_or_cpuset " ,
" mempolicy_mbind " ,
" numa_misplaced " ,
" cma " ,
} ;
mm, printk: introduce new format string for flags
In mm we use several kinds of flags bitfields that are sometimes printed
for debugging purposes, or exported to userspace via sysfs. To make
them easier to interpret independently on kernel version and config, we
want to dump also the symbolic flag names. So far this has been done
with repeated calls to pr_cont(), which is unreliable on SMP, and not
usable for e.g. sysfs export.
To get a more reliable and universal solution, this patch extends
printk() format string for pointers to handle the page flags (%pGp),
gfp_flags (%pGg) and vma flags (%pGv). Existing users of
dump_flag_names() are converted and simplified.
It would be possible to pass flags by value instead of pointer, but the
%p format string for pointers already has extensions for various kernel
structures, so it's a good fit, and the extra indirection in a
non-critical path is negligible.
[linux@rasmusvillemoes.dk: lots of good implementation suggestions]
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Acked-by: Michal Hocko <mhocko@suse.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Sasha Levin <sasha.levin@oracle.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Mel Gorman <mgorman@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-03-16 00:55:56 +03:00
const struct trace_print_flags pageflag_names [ ] = {
__def_pageflag_names ,
{ 0 , NULL }
} ;
const struct trace_print_flags gfpflag_names [ ] = {
__def_gfpflag_names ,
{ 0 , NULL }
mm, tracing: unify mm flags handling in tracepoints and printk
In tracepoints, it's possible to print gfp flags in a human-friendly
format through a macro show_gfp_flags(), which defines a translation
array and passes is to __print_flags(). Since the following patch will
introduce support for gfp flags printing in printk(), it would be nice
to reuse the array. This is not straightforward, since __print_flags()
can't simply reference an array defined in a .c file such as mm/debug.c
- it has to be a macro to allow the macro magic to communicate the
format to userspace tools such as trace-cmd.
The solution is to create a macro __def_gfpflag_names which is used both
in show_gfp_flags(), and to define the gfpflag_names[] array in
mm/debug.c.
On the other hand, mm/debug.c also defines translation tables for page
flags and vma flags, and desire was expressed (but not implemented in
this series) to use these also from tracepoints. Thus, this patch also
renames the events/gfpflags.h file to events/mmflags.h and moves the
table definitions there, using the same macro approach as for gfpflags.
This allows translating all three kinds of mm-specific flags both in
tracepoints and printk.
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Reviewed-by: Michal Hocko <mhocko@suse.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Sasha Levin <sasha.levin@oracle.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Mel Gorman <mgorman@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-03-16 00:55:52 +03:00
} ;
mm, printk: introduce new format string for flags
In mm we use several kinds of flags bitfields that are sometimes printed
for debugging purposes, or exported to userspace via sysfs. To make
them easier to interpret independently on kernel version and config, we
want to dump also the symbolic flag names. So far this has been done
with repeated calls to pr_cont(), which is unreliable on SMP, and not
usable for e.g. sysfs export.
To get a more reliable and universal solution, this patch extends
printk() format string for pointers to handle the page flags (%pGp),
gfp_flags (%pGg) and vma flags (%pGv). Existing users of
dump_flag_names() are converted and simplified.
It would be possible to pass flags by value instead of pointer, but the
%p format string for pointers already has extensions for various kernel
structures, so it's a good fit, and the extra indirection in a
non-critical path is negligible.
[linux@rasmusvillemoes.dk: lots of good implementation suggestions]
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Acked-by: Michal Hocko <mhocko@suse.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Sasha Levin <sasha.levin@oracle.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Mel Gorman <mgorman@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-03-16 00:55:56 +03:00
const struct trace_print_flags vmaflag_names [ ] = {
__def_vmaflag_names ,
{ 0 , NULL }
2014-10-10 02:28:34 +04:00
} ;
2016-03-16 00:56:24 +03:00
void __dump_page ( struct page * page , const char * reason )
2014-10-10 02:28:34 +04:00
{
2018-07-04 03:02:53 +03:00
bool page_poisoned = PagePoisoned ( page ) ;
int mapcount ;
/*
* If struct page is poisoned don ' t access Page * ( ) functions as that
* leads to recursive loop . Page * ( ) check for poisoned pages , and calls
* dump_page ( ) when detected .
*/
if ( page_poisoned ) {
pr_emerg ( " page:%px is uninitialized and poisoned " , page ) ;
goto hex_only ;
}
2016-10-08 03:01:40 +03:00
/*
* Avoid VM_BUG_ON ( ) in page_mapcount ( ) .
* page - > _mapcount space in struct page is used by sl [ aou ] b pages to
* encode own info .
*/
2018-07-04 03:02:53 +03:00
mapcount = PageSlab ( page ) ? 0 : page_mapcount ( page ) ;
2016-09-20 00:44:07 +03:00
2018-01-05 03:17:59 +03:00
pr_emerg ( " page:%px count:%d mapcount:%d mapping:%px index:%#lx " ,
2016-09-20 00:44:07 +03:00
page , page_ref_count ( page ) , mapcount ,
page - > mapping , page_to_pgoff ( page ) ) ;
2016-01-16 03:53:42 +03:00
if ( PageCompound ( page ) )
pr_cont ( " compound_mapcount: %d " , compound_mapcount ( page ) ) ;
pr_cont ( " \n " ) ;
mm, printk: introduce new format string for flags
In mm we use several kinds of flags bitfields that are sometimes printed
for debugging purposes, or exported to userspace via sysfs. To make
them easier to interpret independently on kernel version and config, we
want to dump also the symbolic flag names. So far this has been done
with repeated calls to pr_cont(), which is unreliable on SMP, and not
usable for e.g. sysfs export.
To get a more reliable and universal solution, this patch extends
printk() format string for pointers to handle the page flags (%pGp),
gfp_flags (%pGg) and vma flags (%pGv). Existing users of
dump_flag_names() are converted and simplified.
It would be possible to pass flags by value instead of pointer, but the
%p format string for pointers already has extensions for various kernel
structures, so it's a good fit, and the extra indirection in a
non-critical path is negligible.
[linux@rasmusvillemoes.dk: lots of good implementation suggestions]
Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
Acked-by: Michal Hocko <mhocko@suse.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Sasha Levin <sasha.levin@oracle.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Mel Gorman <mgorman@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2016-03-16 00:55:56 +03:00
BUILD_BUG_ON ( ARRAY_SIZE ( pageflag_names ) ! = __NR_PAGEFLAGS + 1 ) ;
2016-03-16 00:56:24 +03:00
2016-03-16 00:55:59 +03:00
pr_emerg ( " flags: %#lx(%pGp) \n " , page - > flags , & page - > flags ) ;
2018-07-04 03:02:53 +03:00
hex_only :
2016-12-13 03:44:35 +03:00
print_hex_dump ( KERN_ALERT , " raw: " , DUMP_PREFIX_NONE , 32 ,
sizeof ( unsigned long ) , page ,
sizeof ( struct page ) , false ) ;
2014-10-10 02:28:34 +04:00
if ( reason )
pr_alert ( " page dumped because: %s \n " , reason ) ;
2016-03-16 00:55:59 +03:00
2014-12-11 02:44:58 +03:00
# ifdef CONFIG_MEMCG
2018-07-04 03:02:53 +03:00
if ( ! page_poisoned & & page - > mem_cgroup )
2018-01-05 03:17:59 +03:00
pr_alert ( " page->mem_cgroup:%px \n " , page - > mem_cgroup ) ;
2014-12-11 02:44:58 +03:00
# endif
2014-10-10 02:28:34 +04:00
}
void dump_page ( struct page * page , const char * reason )
{
2016-03-16 00:56:24 +03:00
__dump_page ( page , reason ) ;
2016-03-16 00:56:21 +03:00
dump_page_owner ( page ) ;
2014-10-10 02:28:34 +04:00
}
EXPORT_SYMBOL ( dump_page ) ;
# ifdef CONFIG_DEBUG_VM
void dump_vma ( const struct vm_area_struct * vma )
{
2018-01-05 03:17:59 +03:00
pr_emerg ( " vma %px start %px end %px \n "
" next %px prev %px mm %px \n "
" prot %lx anon_vma %px vm_ops %px \n "
" pgoff %lx file %px private_data %px \n "
2016-03-16 00:55:59 +03:00
" flags: %#lx(%pGv) \n " ,
2014-10-10 02:28:34 +04:00
vma , ( void * ) vma - > vm_start , ( void * ) vma - > vm_end , vma - > vm_next ,
vma - > vm_prev , vma - > vm_mm ,
( unsigned long ) pgprot_val ( vma - > vm_page_prot ) ,
vma - > anon_vma , vma - > vm_ops , vma - > vm_pgoff ,
2016-03-16 00:55:59 +03:00
vma - > vm_file , vma - > vm_private_data ,
vma - > vm_flags , & vma - > vm_flags ) ;
2014-10-10 02:28:34 +04:00
}
EXPORT_SYMBOL ( dump_vma ) ;
2014-10-10 02:28:37 +04:00
void dump_mm ( const struct mm_struct * mm )
{
2018-01-05 03:17:59 +03:00
pr_emerg ( " mm %px mmap %px seqnum %d task_size %lu \n "
2014-10-10 02:28:37 +04:00
# ifdef CONFIG_MMU
2018-01-05 03:17:59 +03:00
" get_unmapped_area %px \n "
2014-10-10 02:28:37 +04:00
# endif
" mmap_base %lu mmap_legacy_base %lu highest_vm_end %lu \n "
2018-01-05 03:17:59 +03:00
" pgd %px mm_users %d mm_count %d pgtables_bytes %lu map_count %d \n "
2014-10-10 02:28:37 +04:00
" hiwater_rss %lx hiwater_vm %lx total_vm %lx locked_vm %lx \n "
2016-01-15 02:22:07 +03:00
" pinned_vm %lx data_vm %lx exec_vm %lx stack_vm %lx \n "
2014-10-10 02:28:37 +04:00
" start_code %lx end_code %lx start_data %lx end_data %lx \n "
" start_brk %lx brk %lx start_stack %lx \n "
" arg_start %lx arg_end %lx env_start %lx env_end %lx \n "
2018-01-05 03:17:59 +03:00
" binfmt %px flags %lx core_state %px \n "
2014-10-10 02:28:37 +04:00
# ifdef CONFIG_AIO
2018-01-05 03:17:59 +03:00
" ioctx_table %px \n "
2014-10-10 02:28:37 +04:00
# endif
# ifdef CONFIG_MEMCG
2018-01-05 03:17:59 +03:00
" owner %px "
2014-10-10 02:28:37 +04:00
# endif
2018-01-05 03:17:59 +03:00
" exe_file %px \n "
2014-10-10 02:28:37 +04:00
# ifdef CONFIG_MMU_NOTIFIER
2018-01-05 03:17:59 +03:00
" mmu_notifier_mm %px \n "
2014-10-10 02:28:37 +04:00
# endif
# ifdef CONFIG_NUMA_BALANCING
" numa_next_scan %lu numa_scan_offset %lu numa_scan_seq %d \n "
# endif
" tlb_flush_pending %d \n "
2016-03-16 00:55:59 +03:00
" def_flags: %#lx(%pGv) \n " ,
2014-10-10 02:28:37 +04:00
mm , mm - > mmap , mm - > vmacache_seqnum , mm - > task_size ,
# ifdef CONFIG_MMU
mm - > get_unmapped_area ,
# endif
mm - > mmap_base , mm - > mmap_legacy_base , mm - > highest_vm_end ,
mm - > pgd , atomic_read ( & mm - > mm_users ) ,
atomic_read ( & mm - > mm_count ) ,
2017-11-16 04:35:40 +03:00
mm_pgtables_bytes ( mm ) ,
2014-10-10 02:28:37 +04:00
mm - > map_count ,
mm - > hiwater_rss , mm - > hiwater_vm , mm - > total_vm , mm - > locked_vm ,
2016-01-15 02:22:07 +03:00
mm - > pinned_vm , mm - > data_vm , mm - > exec_vm , mm - > stack_vm ,
2014-10-10 02:28:37 +04:00
mm - > start_code , mm - > end_code , mm - > start_data , mm - > end_data ,
mm - > start_brk , mm - > brk , mm - > start_stack ,
mm - > arg_start , mm - > arg_end , mm - > env_start , mm - > env_end ,
mm - > binfmt , mm - > flags , mm - > core_state ,
# ifdef CONFIG_AIO
mm - > ioctx_table ,
# endif
# ifdef CONFIG_MEMCG
mm - > owner ,
# endif
mm - > exe_file ,
# ifdef CONFIG_MMU_NOTIFIER
mm - > mmu_notifier_mm ,
# endif
# ifdef CONFIG_NUMA_BALANCING
mm - > numa_next_scan , mm - > numa_scan_offset , mm - > numa_scan_seq ,
# endif
mm: migrate: prevent racy access to tlb_flush_pending
Patch series "fixes of TLB batching races", v6.
It turns out that Linux TLB batching mechanism suffers from various
races. Races that are caused due to batching during reclamation were
recently handled by Mel and this patch-set deals with others. The more
fundamental issue is that concurrent updates of the page-tables allow
for TLB flushes to be batched on one core, while another core changes
the page-tables. This other core may assume a PTE change does not
require a flush based on the updated PTE value, while it is unaware that
TLB flushes are still pending.
This behavior affects KSM (which may result in memory corruption) and
MADV_FREE and MADV_DONTNEED (which may result in incorrect behavior). A
proof-of-concept can easily produce the wrong behavior of MADV_DONTNEED.
Memory corruption in KSM is harder to produce in practice, but was
observed by hacking the kernel and adding a delay before flushing and
replacing the KSM page.
Finally, there is also one memory barrier missing, which may affect
architectures with weak memory model.
This patch (of 7):
Setting and clearing mm->tlb_flush_pending can be performed by multiple
threads, since mmap_sem may only be acquired for read in
task_numa_work(). If this happens, tlb_flush_pending might be cleared
while one of the threads still changes PTEs and batches TLB flushes.
This can lead to the same race between migration and
change_protection_range() that led to the introduction of
tlb_flush_pending. The result of this race was data corruption, which
means that this patch also addresses a theoretically possible data
corruption.
An actual data corruption was not observed, yet the race was was
confirmed by adding assertion to check tlb_flush_pending is not set by
two threads, adding artificial latency in change_protection_range() and
using sysctl to reduce kernel.numa_balancing_scan_delay_ms.
Link: http://lkml.kernel.org/r/20170802000818.4760-2-namit@vmware.com
Fixes: 20841405940e ("mm: fix TLB flush race between migration, and
change_protection_range")
Signed-off-by: Nadav Amit <namit@vmware.com>
Acked-by: Mel Gorman <mgorman@suse.de>
Acked-by: Rik van Riel <riel@redhat.com>
Acked-by: Minchan Kim <minchan@kernel.org>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Hugh Dickins <hughd@google.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Jeff Dike <jdike@addtoit.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Mel Gorman <mgorman@techsingularity.net>
Cc: Russell King <linux@armlinux.org.uk>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2017-08-11 01:23:56 +03:00
atomic_read ( & mm - > tlb_flush_pending ) ,
2016-03-16 00:55:59 +03:00
mm - > def_flags , & mm - > def_flags
) ;
2014-10-10 02:28:37 +04:00
}
2014-10-10 02:28:34 +04:00
# endif /* CONFIG_DEBUG_VM */