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/notify/Makefile

ebb3b47e - fsnotify: Drop inode_mark.c

Wed, 21 Dec 2016 15:40:48 +0000

fsnotify: Drop inode_mark.cinode_mark.c now contains only a single function. Move it tofs/notify/fsnotify.c and remove inode_mark.c.Reviewed-by: Miklos Szeredi Reviewed-by: Amir Goldstein Signed-off-by: Jan Kara List of files: /linux-6.15/fs/notify/Makefile

b1362edf - fsnotify: Remove fsnotify_find_{inode|vfsmount}_mark()

Wed, 21 Dec 2016 15:28:45 +0000

fsnotify: Remove fsnotify_find_{inode|vfsmount}_mark()These are very thin wrappers, just remove them. Dropfs/notify/vfsmount_mark.c as it is empty now.Reviewed-by: Miklos Szeredi Reviewed-by: Amir Goldstein Signed-off-by: Jan Kara List of files: /linux-6.15/fs/notify/Makefile

be77196b - fs, notify: add procfs fdinfo helper

Tue, 18 Dec 2012 00:05:12 +0000

fs, notify: add procfs fdinfo helperThis allow us to print out fsnotify details such as watchee inode, device,mask and optionally a file handle.For inotify objects if kernel compiled with exportfs support the outputwill be | pos: 0 | flags: 02000000 | inotify wd:3 ino:9e7e sdev:800013 mask:800afce ignored_mask:0 fhandle-bytes:8 fhandle-type:1 f_handle:7e9e0000640d1b6d | inotify wd:2 ino:a111 sdev:800013 mask:800afce ignored_mask:0 fhandle-bytes:8 fhandle-type:1 f_handle:11a1000020542153 | inotify wd:1 ino:6b149 sdev:800013 mask:800afce ignored_mask:0 fhandle-bytes:8 fhandle-type:1 f_handle:49b1060023552153If kernel compiled without exportfs support, the file handlewon't be provided but inode and device only. | pos: 0 | flags: 02000000 | inotify wd:3 ino:9e7e sdev:800013 mask:800afce ignored_mask:0 | inotify wd:2 ino:a111 sdev:800013 mask:800afce ignored_mask:0 | inotify wd:1 ino:6b149 sdev:800013 mask:800afce ignored_mask:0For fanotify the output is like | pos: 0 | flags: 04002 | fanotify flags:10 event-flags:0 | fanotify mnt_id:12 mask:3b ignored_mask:0 | fanotify ino:50205 sdev:800013 mask:3b ignored_mask:40000000 fhandle-bytes:8 fhandle-type:1 f_handle:05020500fb1d47e7To minimize impact on general fsnotify code the new functionalityis gathered in fs/notify/fdinfo.c file.Signed-off-by: Cyrill Gorcunov Acked-by: Pavel Emelyanov Cc: Oleg Nesterov Cc: Andrey Vagin Cc: Al Viro Cc: Alexey Dobriyan Cc: James Bottomley Cc: "Aneesh Kumar K.V" Cc: Alexey Dobriyan Cc: Matthew Helsley Cc: "J. Bruce Fields" Cc: "Aneesh Kumar K.V" Cc: Tvrtko Ursulin Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/notify/Makefile

0d48b7f0 - fsnotify: vfsmount marks generic functions

Fri, 18 Dec 2009 02:24:27 +0000

fsnotify: vfsmount marks generic functionsMuch like inode-mark.c has all of the code dealing with marks on inodesthis patch adds a vfsmount-mark.c which has similar code but is intendedfor marks on vfsmounts.Signed-off-by: Eric Paris List of files: /linux-6.15/fs/notify/Makefile

5444e298 - fsnotify: split generic and inode specific mark code

Fri, 18 Dec 2009 02:24:27 +0000

fsnotify: split generic and inode specific mark codecurrently all marking is done by functions in inode-mark.c. Some of thisis pretty generic and should be instead done in a generic function and weshould only put the inode specific code in inode-mark.cSigned-off-by: Eric Paris List of files: /linux-6.15/fs/notify/Makefile

ff0b16a9 - fanotify: fscking all notification system

Fri, 18 Dec 2009 02:24:25 +0000

fanotify: fscking all notification systemfanotify is a novel file notification system which bases notification ongiving userspace both an event type (open, close, read, write) and an openfile descriptor to the object in question. This should address a number ofraces and problems with other notification systems like inotify and dnotifyand should allow the future implementation of blocking or access controllednotification. These are useful for on access scanners or hierachical storagemanagement schemes.This patch just implements the basics of the fsnotify functions.Signed-off-by: Eric Paris List of files: /linux-6.15/fs/notify/Makefile

3be25f49 - fsnotify: add marks to inodes so groups can interpret how to handle those inodes

Thu, 21 May 2009 21:01:26 +0000

fsnotify: add marks to inodes so groups can interpret how to handle those inodesThis patch creates a way for fsnotify groups to attach marks to inodes.These marks have little meaning to the generic fsnotify infrastructureand thus their meaning should be interpreted by the group that attachedthem to the inode's list.dnotify and inotify will make use of these markings to indicate whichinodes are of interest to their respective groups. But this implementationhas the useful property that in the future other listeners could actuallyuse the marks for the exact opposite reason, aka to indicate which inodesit had NO interest in.Signed-off-by: Eric Paris Acked-by: Al Viro Cc: Christoph Hellwig List of files: /linux-6.15/fs/notify/Makefile

90586523 - fsnotify: unified filesystem notification backend

Thu, 21 May 2009 21:01:20 +0000

fsnotify: unified filesystem notification backendfsnotify is a backend for filesystem notification. fsnotify doesnot provide any userspace interface but does provide the basisneeded for other notification schemes such as dnotify. fsnotifycan be extended to be the backend for inotify or the upcomingfanotify. fsnotify provides a mechanism for "groups" to register forsome set of filesystem events and to then deliver those events tothose groups for processing.fsnotify has a number of benefits, the first being actually shrinking the sizeof an inode. Before fsnotify to support both dnotify and inotify an inode had unsigned long i_dnotify_mask; /* Directory notify events */ struct dnotify_struct *i_dnotify; /* for directory notifications */ struct list_head inotify_watches; /* watches on this inode */ struct mutex inotify_mutex; /* protects the watches listBut with fsnotify this same functionallity (and more) is done with just __u32 i_fsnotify_mask; /* all events for this inode */ struct hlist_head i_fsnotify_mark_entries; /* marks on this inode */That's right, inotify, dnotify, and fanotify all in 64 bits. We used thatmuch space just in inotify_watches alone, before this patch set.fsnotify object lifetime and locking is MUCH better than what we have today.inotify locking is incredibly complex. See 8f7b0ba1c8539 as an example ofwhat's been busted since inception. inotify needs to know internal semanticsof superblock destruction and unmounting to function. The inode pinning andvfs contortions are horrible.no fsnotify implementers do allocation under locks. This means things likef04b30de3 which (due to an overabundance of caution) changes GFP_KERNEL toGFP_NOFS can be reverted. There are no longer any allocation rules when usingor implementing your own fsnotify listener.fsnotify paves the way for fanotify. In brief fanotify is a notificationmechanism that delivers the lisener both an 'event' and an open file descriptorto the object in question. This means that fanotify is pathname agnostic.Some on lkml may not care for the original companies or users that pushed forTALPA, but fanotify was designed with flexibility and input for other users inmind. The readahead group expressed interest in fanotify as it could be usedto profile disk access on boot without breaking the audit system. The desktopsearch groups have also expressed interest in fanotify as it solves a numberof the race conditions and problems present with managing inotify when morethan a limited number of specific files are of interest. fanotify can providefor a userspace access control system which makes it a clean interface for AVvendors to hook without trying to do binary patching on the syscall table,LSM, and everywhere else they do their things today. With this patch seriesfanotify can be implemented in less than 1200 lines of easy to review code.Almost all of which is the socket based user interface.This patch series builds fsnotify to the point that it can implementdnotify and inotify_user. Patches exist and will be sent soon afteracceptance to finish the in kernel inotify conversion (audit) and implementfanotify.Signed-off-by: Eric Paris Acked-by: Al Viro Cc: Christoph Hellwig List of files: /linux-6.15/fs/notify/Makefile

272eb014 - filesystem notification: create fs/notify to contain all fs notification

Wed, 17 Dec 2008 18:59:41 +0000

filesystem notification: create fs/notify to contain all fs notificationCreating a generic filesystem notification interface, fsnotify, which will beused by inotify, dnotify, and eventually fanotify is really starting toclutter the fs directory. This patch simply moves inotify and dnotify intofs/notify/inotify and fs/notify/dnotify respectively to make both current fs/and future notification tidier.Signed-off-by: Eric Paris Signed-off-by: Al Viro List of files: /linux-6.15/fs/notify/Makefile