1. 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
  2. 01 Jun, 2012 1 commit
  3. 26 Oct, 2010 1 commit
  4. 31 Mar, 2009 2 commits
  5. 21 Feb, 2009 1 commit
  6. 06 Jan, 2009 1 commit
  7. 01 Nov, 2008 1 commit
  8. 30 Oct, 2008 1 commit
  9. 16 Oct, 2008 1 commit
  10. 12 Oct, 2008 4 commits
    • Arjan van de Ven's avatar
      raid: make RAID autodetect default a KConfig option · a364092a
      Arjan van de Ven authored
      RAID autodetect has the side effect of requiring synchronisation
      of all device drivers, which can make the boot several seconds longer
      (I've measured 7 on one of my laptops).... even for systems that don't
      have RAID setup for the root filesystem (the only FS where this matters).
      
      This patch makes the default for autodetect a config option; either way
      the user can always override via the kernel command line.
      Signed-off-by: default avatarArjan van de Ven <arjan@linux.intel.com>
      Acked-by: default avatarNeilBrown <neilb@suse.de>
      a364092a
    • Ingo Molnar's avatar
      warning: fix init do_mounts_md c · 82cbc11a
      Ingo Molnar authored
      fix warning:
      
        init/do_mounts_md.c: In function ‘md_run_setup’:
        init/do_mounts_md.c:282: warning: ISO C90 forbids mixed declarations and code
      
      also, use the opportunity to put the RAID autodetection code
      into a separate function - this also solves a checkpatch style warning.
      
      No code changed:
      
      md5:
         aa36a35faef371b05f1974ad583bdbbd  do_mounts_md.o.before.asm
         aa36a35faef371b05f1974ad583bdbbd  do_mounts_md.o.after.asm
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      82cbc11a
    • Arjan van de Ven's avatar
      fastboot: make the RAID autostart code print a message just before waiting · 02c15def
      Arjan van de Ven authored
      As requested/suggested by Neil Brown: make the raid code print that it's
      about to wait for probing to be done as well as give a suggestion on how
      to disable the probing if the user doesn't use raid.
      
      Signed-off-by: Arjan van de Ven <arjan@linux.intel.com
      02c15def
    • Arjan van de Ven's avatar
      fastboot: make the raid autodetect code wait for all devices to init · 589f800b
      Arjan van de Ven authored
      The raid autodetect code really needs to have all devices probed before
      it can detect raid arrays; not doing so would give rather messy situations
      where arrays would get detected as degraded while they shouldn't be etc.
      
      This is in preparation of removing the "wait for everything to init"
      code that makes everyone pay, not just raid users.
      Signed-off-by: default avatarArjan van de Ven <arjan@linux.intel.com>
      589f800b
  11. 24 May, 2008 1 commit
  12. 29 Apr, 2008 1 commit
  13. 03 Oct, 2006 1 commit
  14. 26 Jun, 2006 1 commit
  15. 06 Jan, 2006 1 commit
    • NeilBrown's avatar
      [PATCH] md: remove personality numbering from md · 2604b703
      NeilBrown authored
      md supports multiple different RAID level, each being implemented by a
      'personality' (which is often in a separate module).
      
      These personalities have fairly artificial 'numbers'.  The numbers
      are use to:
       1- provide an index into an array where the various personalities
          are recorded
       2- identify the module (via an alias) which implements are particular
          personality.
      
      Neither of these uses really justify the existence of personality numbers.
      The array can be replaced by a linked list which is searched (array lookup
      only happens very rarely).  Module identification can be done using an alias
      based on level rather than 'personality' number.
      
      The current 'raid5' modules support two level (4 and 5) but only one
      personality.  This slight awkwardness (which was handled in the mapping from
      level to personality) can be better handled by allowing raid5 to register 2
      personalities.
      
      With this change in place, the core md module does not need to have an
      exhaustive list of all possible personalities, so other personalities can be
      added independently.
      
      This patch also moves the check for chunksize being non-zero into the ->run
      routines for the personalities that need it, rather than having it in core-md.
       This has a side effect of allowing 'faulty' and 'linear' not to have a
      chunk-size set.
      Signed-off-by: default avatarNeil Brown <neilb@suse.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      2604b703
  16. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4