Changes in Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense 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 bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe 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 caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase 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 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately 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 licenseidentifiers 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 thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion 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 correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/fs/9p/Makefile

e409de99 - 9p: xattr simplifications

Sun, 04 Oct 2015 17:18:52 +0000

9p: xattr simplificationsNow that the xattr handler is passed to the xattr handler operations, wecan use the same get and set operations for the user, trusted, and securityxattr namespaces. In those namespaces, we can access the full attributename by "reattaching" the name prefix the vfs has skipped for us. Add axattr_full_name helper to make this obvious in the code.For the "system.posix_acl_access" and "system.posix_acl_default"attributes, handler->prefix is the full attribute name; the suffix is theempty string.Signed-off-by: Andreas Gruenbacher Cc: Eric Van Hensbergen Cc: Ron Minnich Cc: Latchesar Ionkov Cc: v9fs-developer@lists.sourceforge.netSigned-off-by: Al Viro List of files: /linux-6.15/fs/9p/Makefile

d9a73859 - fs/9p: xattr: add trusted and security namespaces

Wed, 29 May 2013 19:09:39 +0000

fs/9p: xattr: add trusted and security namespacesAllow requests for security.* and trusted.* xattr name spacesto pass through to server.The new files are 99% cut and paste from fs/9p/xattr_user.c with thenamespaces changed. It has the intended effect in superficial testing.I do not know much detail about how these namespaces are used, but passingthem through to the server, which can decide whether to handle them or not,seems reasonable.I want to support a use case where an ext4 file system is mounted via 9P,then re-exported via samba to windows clients in a cluster. Windows wantsto store xattrs such as security.NTACL. This works when ext4 directlybacks samba, but not when 9P is inserted. This use case is documented here: http://code.google.com/p/diod/issues/detail?id=95Signed-off-by: Jim Garlick Signed-off-by: Eric Van Hensbergen List of files: /linux-6.15/fs/9p/Makefile

53c06f4e - fs/9p: Move dotl inode operations into a seperate file

Mon, 10 Jan 2011 19:51:47 +0000

fs/9p: Move dotl inode operations into a seperate fileSource Code ReorganizationSigned-off-by: Aneesh Kumar K.V Signed-off-by: Venkateswararao Jujjuri Signed-off-by: Eric Van Hensbergen List of files: /linux-6.15/fs/9p/Makefile

85ff872d - fs/9p: Implement POSIX ACL permission checking function

Mon, 27 Sep 2010 18:57:39 +0000

fs/9p: Implement POSIX ACL permission checking functionThe ACL value is fetched as a part of inode initializationfrom the server and the permission checking function use thecached value of the ACLSigned-off-by: Aneesh Kumar K.V Signed-off-by: Venkateswararao Jujjuri Signed-off-by: Eric Van Hensbergen List of files: /linux-6.15/fs/9p/Makefile

ebf46264 - fs/9p: Add support user. xattr

Mon, 31 May 2010 07:52:56 +0000

fs/9p: Add support user. xattrSigned-off-by: Aneesh Kumar K.V Signed-off-by: Venkateswararao Jujjuri Signed-off-by: Eric Van Hensbergen List of files: /linux-6.15/fs/9p/Makefile

60e78d2c - 9p: Add fscache support to 9p

Wed, 23 Sep 2009 18:00:27 +0000

9p: Add fscache support to 9pThis patch adds a persistent, read-only caching facility for9p clients using the FS-Cache caching backend.When the fscache facility is enabled, each inode is associatedwith a corresponding vcookie which is an index into the FS-Cacheindexing tree. The FS-Cache indexing tree is indexed at 3 levels:- session object associated with each mount.- inode/vcookie- actual data (pages)A cache tag is chosen randomly for each session. These tags canbe read off /sys/fs/9p/caches and can be passed as a mount-timeparameter to re-attach to the specified caching session.Signed-off-by: Abhishek Kulkarni Signed-off-by: Eric Van Hensbergen List of files: /linux-6.15/fs/9p/Makefile

bd238fb4 - 9p: Reorganization of 9p file system code

Tue, 10 Jul 2007 22:57:28 +0000

9p: Reorganization of 9p file system codeThis patchset moves non-filesystem interfaces of v9fs from fs/9p to net/9p.It moves the transport, packet marshalling and connection layers to net/9pleaving only the VFS related files in fs/9p. This work is being done inpreparation for in-kernel 9p servers as well as alternate 9p clients (otherthan VFS).Signed-off-by: Latchesar Ionkov Signed-off-by: Eric Van Hensbergen List of files: /linux-6.15/fs/9p/Makefile

67543e50 - [PATCH] 9p: fix name consistency problems

Sat, 25 Mar 2006 11:07:29 +0000

[PATCH] 9p: fix name consistency problemsThere were a number of conflicting naming schemes used in the v9fs project.The directory was fs/9p, but MAINTAINERS and Documentation referred tov9fs. The module name itself was 9p2000, and the file system type was 9P.This patch attempts to clean that up, changing all references to 9p inorder to match the directory name. We'll also start using 9p instead ofv9fs as our patch prefix.There is also a minor consistency cleanup in the options changing the nameoption to uname in order to more closely match the Plan 9 options.Signed-off-by: Eric Van Hensbergevan Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/9p/Makefile

5174fdab - [PATCH] v9fs: print 9p messages

Sat, 25 Mar 2006 11:07:25 +0000

[PATCH] v9fs: print 9p messagesPrint 9p messages.Signed-off-by: Latchesar Ionkov Cc: Eric Van Hensbergen Signed-off-by: Adrian Bunk Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/9p/Makefile

27979bb2 - [PATCH] v9fs: consolidate trans_sock into trans_fd

Sat, 25 Mar 2006 11:07:23 +0000

[PATCH] v9fs: consolidate trans_sock into trans_fdHere is a new trans_fd.c that replaces the current trans_fd.c andtrans_sock.c.Signed-off-by: Eric Van Hensbergen Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/9p/Makefile

147b31cf - [PATCH] v9fs: add readpage support

Thu, 19 Jan 2006 01:43:02 +0000

[PATCH] v9fs: add readpage supportv9fs mmap support was originally removed from v9fs at Al Viro's request,but recently there have been requests from folks who want readpagefunctionality (primarily to enable execution of files mounted via 9P).This patch adds readpage support (but not writepage which contained most ofthe objectionable code). It passes fsx-linux (and other regressions) so itshould be relatively safe.Signed-off-by: Eric Van Hensbergen Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/9p/Makefile

531b1094 - [PATCH] v9fs: zero copy implementation

Sun, 08 Jan 2006 09:05:00 +0000

[PATCH] v9fs: zero copy implementationPerformance enhancement reducing the number of copies in the data andstat paths.Signed-off-by: Latchesar Ionkov Cc: Eric Van Hensbergen Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/9p/Makefile

93fa58cb - [PATCH] v9fs: Documentation, Makefiles, Configuration

Fri, 09 Sep 2005 20:04:18 +0000

[PATCH] v9fs: Documentation, Makefiles, ConfigurationOVERVIEWV9FS is a distributed file system for Linux which provides animplementation of the Plan 9 resource sharing protocol 9P. It can beused to share all sorts of resources: static files, synthetic file servers(such as /proc or /sys), devices, and application file servers (such asFUSE).BACKGROUNDPlan 9 (http://plan9.bell-labs.com/plan9) is a research operatingsystem and associated applications suite developed by the ComputingScience Research Center of AT&T Bell Laboratories (now a part ofLucent Technologies), the same group that developed UNIX , C, and C++.Plan 9 was initially released in 1993 to universities, and then madegenerally available in 1995. Its core operating systems code laid thefoundation for the Inferno Operating System released as a product byLucent Bell-Labs in 1997. The Inferno venture was the only commercialembodiment of Plan 9 and is currently maintained as a product by VitaNuova (http://www.vitanuova.com). After updated releases in 2000 and2002, Plan 9 was open-sourced under the OSI approved Lucent PublicLicense in 2003.The Plan 9 project was started by Ken Thompson and Rob Pike in 1985.Their intent was to explore potential solutions to some of theshortcomings of UNIX in the face of the widespread use of high-speednetworks to connect machines. In UNIX, networking was an afterthoughtand UNIX clusters became little more than a network of stand-alonesystems. Plan 9 was designed from first principles as a seamlessdistributed system with integrated secure network resource sharing.Applications and services were architected in such a way as to allowfor implicit distribution across a cluster of systems. Configuring anenvironment to use remote application components or services in placeof their local equivalent could be achieved with a few simple commandline instructions. For the most part, application implementationsoperated independent of the location of their actual resources.Commercial operating systems haven't changed much in the 20 yearssince Plan 9 was conceived. Network and distributed systems support isprovided by a patchwork of middle-ware, with an endless number ofpackages supplying pieces of the puzzle. Matters are complicated bythe use of different complicated protocols for individual services,and separate implementations for kernel and application resources.The V9FS project (http://v9fs.sourceforge.net) is an attempt to bringPlan 9's unified approach to resource sharing to Linux and otheroperating systems via support for the 9P2000 resource sharingprotocol.V9FS HISTORYV9FS was originally developed by Ron Minnich and Maya Gokhale at LosAlamos National Labs (LANL) in 1997. In November of 2001, Greg Watsonsetup a SourceForge project as a public repository for the code whichsupported the Linux 2.4 kernel.About a year ago, I picked up the initial attempt Ron Minnich hadmade to provide 2.6 support and got the code integrated into a 2.6.5kernel. I then went through a line-for-line re-write attempting toclean-up the code while more closely following the Linux Kernel styleguidelines. I co-authored a paper with Ron Minnich on the V9FS Linuxsupport including performance comparisons to NFSv3 using Bonnie andPostMark - this paper appeared at the USENIX/FREENIX 2005conference in April 2005:( http://www.usenix.org/events/usenix05/tech/freenix/hensbergen.html ).CALL FOR PARTICIPATION/REQUEST FOR COMMENTSOur 2.6 kernel support is stabilizing and we'd like to begin pursuingits integration into the official kernel tree. We would appreciate anyreview, comments, critiques, and additions from this community and areactively seeking people to join our project and help us producesomething that would be acceptable and useful to the Linux community.STATUSThe code is reasonably stable, although there are no doubt corner casesour regression tests haven't discovered yet. It is in regular use by severalof the developers and has been tested on x86 and PowerPC(32-bit and 64-bit) in both small and large (LANL cluster) deployments.Our current regression tests include fsx, bonnie, and postmark.It was our intention to keep things as simple as possible for thisrelease -- trying to focus on correctness within the core of theprotocol support versus a rich set of features. For example: a morecomplete security model and cache layer are in the road map, butexcluded from this release. Additionally, we have removed support formmap operations at Al Viro's request.PERFORMANCEDetailed performance numbers and analysis are included in the FREENIXpaper, but we show comparable performance to NFSv3 for large fileoperations based on the Bonnie benchmark, and superior performance formany small file operations based on the PostMark benchmark. Somewhatpreliminary graphs (from the FREENIX paper) are available(http://v9fs.sourceforge.net/perf/index.html).RESOURCESThe source code is available in a few different forms:tarballs: http://v9fs.sf.netCVSweb: http://cvs.sourceforge.net/viewcvs.py/v9fs/linux-9p/CVS: :pserver:anonymous@cvs.sourceforge.net:/cvsroot/v9fs/linux-9pGit: rsync://v9fs.graverobber.org/v9fs (webgit: http://v9fs.graverobber.org)9P: tcp!v9fs.graverobber.org!6564The user-level server is available from either the Plan 9 distributionor from http://v9fs.sf.netOther support applications are still being developed, but preliminaryversion can be downloaded from sourceforge.Documentation on the protocol has historically been the Plan 9 Manpages (http://plan9.bell-labs.com/sys/man/5/INDEX.html), but there isan effort under way to write a more complete Internet-Draft stylespecification (http://v9fs.sf.net/rfc).There are a couple of mailing lists supporting v9fs, but the most usedis v9fs-developer@lists.sourceforge.net -- please direct/cc yourcomments there so the other v9fs contibutors can participate in theconversation. There is also an IRC channel: irc://freenode.net/#v9fsThis part of the patch contains Documentation, Makefiles, and configurationfile changes.Signed-off-by: Eric Van Hensbergen Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/9p/Makefile