1. 16 Nov, 2017 1 commit
  2. 02 Nov, 2017 1 commit
    • Greg Kroah-Hartman's avatar
      License cleanup: add SPDX GPL-2.0 license identifier to files with no license · b2441318
      Greg Kroah-Hartman authored
      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: default avatarKate Stewart <kstewart@linuxfoundation.org>
      Reviewed-by: default avatarPhilippe Ombredanne <pombredanne@nexb.com>
      Reviewed-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b2441318
  3. 12 Apr, 2017 1 commit
  4. 24 May, 2016 1 commit
  5. 01 Jul, 2015 1 commit
  6. 19 May, 2015 1 commit
  7. 02 Apr, 2015 1 commit
  8. 24 Mar, 2015 1 commit
  9. 05 Jan, 2015 2 commits
  10. 09 Nov, 2011 1 commit
  11. 01 Nov, 2011 1 commit
  12. 27 Oct, 2010 1 commit
    • David Howells's avatar
      Partially revert patch that encloses asm-offset.h numbers in brackets · 95a2f6f7
      David Howells authored
      Partially revert patch:
      
      	commit 3234282f
      	Author: Jan Beulich <JBeulich@novell.com>
      	Date:   Tue Oct 19 14:52:26 2010 +0100
      	x86, asm: Fix CFI macro invocations to deal with shortcomings in gas
      
      This breaks MN10300 arch as this changes many instances of instructions
      similar to the following:
      
      	MOV	number,D0
      
      which represents an immediate value load into:
      
      	MOV	(number),D0
      
      which the assembler then interprets as a load from absolute address.
      
      arch/mn10300/kernel/entry.S:64: Error: Invalid opcode/operands
      arch/mn10300/kernel/entry.S:65: Error: junk at end of line, first unrecognized character is `0'
      arch/mn10300/kernel/entry.S:74: Error: Invalid opcode/operands
      arch/mn10300/kernel/entry.S:74: Error: junk at end of line, first unrecognized character is `1'
      arch/mn10300/kernel/entry.S:75: Error: Invalid opcode/operands
      arch/mn10300/kernel/entry.S:76: Error: junk at end of line, first unrecognized character is `0'
      
      cc: Jan Beulich <jbeulich@novell.com>
      cc: Alexander van Heukelum <heukelum@fastmail.fm>
      cc: H. Peter Anvin <hpa@linux.intel.com>
      cc: Ingo Molnar <mingo@elte.hu>
      Signed-off-by: default avatarDavid Howells <dhowells@redhat.com>
      95a2f6f7
  13. 22 Oct, 2010 1 commit
  14. 19 Oct, 2010 1 commit
    • Jan Beulich's avatar
      x86, asm: Fix CFI macro invocations to deal with shortcomings in gas · 3234282f
      Jan Beulich authored
      gas prior to (perhaps) 2.16.90 has problems with passing non-
      parenthesized expressions containing spaces to macros. Spaces, however,
      get inserted by cpp between any macro expanding to a number and a
      subsequent + or -. For the +, current x86 gas then removes the space
      again (future gas may not do so), but for the - the space gets retained
      and is then considered a separator between macro arguments.
      
      Fix the respective definitions for both the - and + cases, so that they
      neither contain spaces nor make cpp insert any (the latter by adding
      seemingly redundant parentheses).
      Signed-off-by: default avatarJan Beulich <jbeulich@novell.com>
      LKML-Reference: <4CBDBEBA020000780001E05A@vpn.id2.novell.com>
      Cc: Alexander van Heukelum <heukelum@fastmail.fm>
      Signed-off-by: default avatarH. Peter Anvin <hpa@linux.intel.com>
      3234282f
  15. 11 Mar, 2010 1 commit
  16. 12 Dec, 2009 2 commits
  17. 25 Jul, 2008 1 commit
  18. 19 May, 2008 1 commit
  19. 28 Apr, 2008 2 commits
  20. 11 Oct, 2007 2 commits
  21. 16 Jul, 2007 1 commit
  22. 02 May, 2007 1 commit
    • Sam Ravnborg's avatar
      kbuild: complain about missing system calls · c53aeca0
      Sam Ravnborg authored
      Most system calls seems to get added to i386 first. This patch
      automatically generates a warning for any new system call which is
      implemented on i386 but not the architecture currently being compiled.
      On PowerPC at the moment, for example, it results in these warnings:
      init/missing_syscalls.h:935:3: warning: #warning syscall sync_file_range not implemented
      init/missing_syscalls.h:947:3: warning: #warning syscall getcpu not implemented
      init/missing_syscalls.h:950:3: warning: #warning syscall epoll_pwait not implemented
      
      The file scripts/checksyscalls.sh list a number of legacy system calls
      that are ignored because they only makes sense on i386 systems.
      
      Other contributors to this patch are Russell King <rmk+lkml@arm.linux.org.uk>
      and Stéphane Jourdois <kwisatz@rubis.org>
      Signed-off-by: default avatarDavid Woodhouse <dwmw2@infradead.org>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      c53aeca0
  23. 25 Sep, 2006 1 commit
    • Olaf Hering's avatar
      remove RPM_BUILD_ROOT from asm-offsets.h · 65ff22ee
      Olaf Hering authored
      No file in rpm binary package should have the RPM_BUILD_ROOT string in it.
      To simplify building of external modules, our kernel-source package
      contains some temp files from the Kbuild system.  asm/asm-offsets.h is one
      of the files that contains the absolute path if make O=$O is used.
      
        * This file was generated by /var/tmp/kernel-source-2.6.14_rc4-build/usr/src/linux-2.6.14-rc4-2/Kbuild
      
      Remove the $RPM_BUILD_ROOT string in the shipped tempfile.
      Signed-off-by: default avatarOlaf Hering <olh@suse.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      65ff22ee
  24. 05 Apr, 2006 1 commit
  25. 08 Jan, 2006 1 commit
  26. 10 Sep, 2005 1 commit
  27. 09 Sep, 2005 2 commits
    • Sam Ravnborg's avatar
      kbuild: mips use generic asm-offsets.h support · 048eb582
      Sam Ravnborg authored
      Removed obsolete stuff from arch makefile.
      mips had a special rule for generating asm-offsets.h so preserved it
      using an architecture specific hook in top-level Kbuild file.
      Renamed .h file to asm-offsets.h
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      048eb582
    • Sam Ravnborg's avatar
      kbuild: full dependency check on asm-offsets.h · 86feeaa8
      Sam Ravnborg authored
      Building asm-offsets.h has been moved to a seperate Kbuild file
      located in the top-level directory. This allow us to share the
      functionality across the architectures.
      
      The old rules in architecture specific Makefiles will die
      in subsequent patches.
      
      Furhtermore the usual kbuild dependency tracking is now used
      when deciding to rebuild asm-offsets.s. So we no longer risk
      to fail a rebuild caused by asm-offsets.c dependencies being touched.
      
      With this common rule-set we now force the same name across
      all architectures. Following patches will fix the rest.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      86feeaa8